We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.
For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.
Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.
After further conversation with Optimizely support it seems like this functionality is not 100% what you would expect (Support ticket 1236742).
It seems like the editorial domains does not support browsing the actual website since you're unable to set the default culture of the edit hostname.
You can see the startpage but any internal links will give you a 404 since the url resolver and Url.Contentlink helper will not add the culture specific path it needs when a culture is not set on a hostname (which you can't on the editorial domain).
I, my colleagues and the customer editors; we have all expect the editorial domains to be browsable but they're not.
So I deem this to still be relevant feedback.
Please enable editors to surf the editorial hostnames as expected.
This is apparently already a feature a colleague informed me about.
Haven't noticed / seen the edit option in the hostname settings before.
But it's quite strange that the Edit option doesn't allow to set language