ideas
ideas copied to clipboard
statamic
Double language switchers in the CP can be confusing
Bug Description
When viewing localized collections you get a second language switcher in the CP. You have the default one in the top navigation bar and the second one above the entries list.
I can imagine this being confusing as the top one suggests to me it's either English or Dutch. One or the other.
As I understand the top picker sets the default for as you navigate through the CP. That's useful. The bottom one is just temporary for the context of the thing you're looking at. The bottom one makes it possible to view English pages when you clearly said you wanted just Dutch. Maybe it could be removed all together?
Or....?
I totally agree. It's kinda useless to have both. In a scenario, in which sites and locales would be different (see my idea here), it would make more sense.
I generally believe that multisite is a bit of a weird mix in V3 right now. Cause basically, every language you wanna add is a new site. Got that. But imagine a restaurant with a few locations, each location being their own site. Wanna add multiple languages to those? Sure possible, but very confusing to use. That's where the groups would come in handy for which the top selector would be a perfect fit for.
Like, just a wrapper on what to display, depending on what site/group is selected above.
Great suggestion @AndreasSchantl! It would be great to separate sites into groups. It feels off that (in your example) location1.restaurant.com and location2.restaurant.com are on the same level als location1.restaurant.com/en.
Not quite sure what you mean with the same level, but using your domains above, it would be like that:
Restaurant 1:
- location1.restaurant.com
- location1.restaurant.com/en
Restaurant 2:
- location2.restaurant.com
- location2.restaurant.com/en
So imagine you have selected Restaurant 1 at the top selector, you would only be able to switch between the two sites of restaurant 1.
Yes. We totally agree!
What I mean with 'the same level' is that a localized site (/en) is currently the same thing as a multisite (location2.). That's a bit weird to me. Your proposed grouping could solve that and make the selectors useful.
Oh yeah, that's true. But I think that they wouldn't change that as that would mess up the whole folder structure. The groups would only be a top layer to not have to mess up the folder structure. But we do mean the same thing đŸ˜„