Current Localization module provides a culture selector shape (FrontEndCultureSelector) for front-end that allows user to change to a different culture but it always redirects user to the home page instead of redirecting you to the culture version of the current page.
There is an alternative for pages with LocalizationPart that allows you to show links for the different cultures for which that page is available.
Problem is I have dynamic forms without LocalizationPart using a visibility rule based on the user language to decide which fields to show.
Another problem of current FrontEndCultureSelector is unexpectedly it forces you to use LocalizationPart in your home page. Furthermore, any content you get through Ajax won't be localized because by default cookie by default it is not used, you need to customize it.
In a site with some pages with LocalizationPart and other without it but with different appearance depending on the language problems arise for usability. The point is FrontEndCultureSelector and LocalizationPart shape doesn't provide a consistent way for changing culture. One redirects the user to the home page, and the other is only available sometimes.
Current Localization module provides a culture selector shape (FrontEndCultureSelector) for front-end that allows user to change to a different culture but it always redirects user to the home page instead of redirecting you to the culture version of the current page.
There is an alternative for pages with LocalizationPart that allows you to show links for the different cultures for which that page is available.
Problem is I have dynamic forms without LocalizationPart using a visibility rule based on the user language to decide which fields to show.
Another problem of current FrontEndCultureSelector is unexpectedly it forces you to use LocalizationPart in your home page. Furthermore, any content you get through Ajax won't be localized because by default cookie by default it is not used, you need to customize it.
In a site with some pages with LocalizationPart and other without it but with different appearance depending on the language problems arise for usability. The point is FrontEndCultureSelector and LocalizationPart shape doesn't provide a consistent way for changing culture. One redirects the user to the home page, and the other is only available sometimes.