You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When clients decide to add additional languages after the initial launch of a website the current logic of this extension only allows them to see/use/edit the new language in the backend, but it is not possible to show it in the frontend without making it accessible to the public.
For smaller websites this might be no big deal, but for larger projects, that take time to translate and fill in all the content for a new language, this is far from perfect – so the wish to temporarily mark languages as 'restricted' and thus make them accessible to logged-in authors in the frontend without involving them in any routing/redirecting-logic for public users popped up quite a few times in the past and I finally decided to implent this, as two cleints actively require this feature.
Might take this as an opportunity to also finish the documentation and finally publish version 2.0.0 of this extension 😶
The text was updated successfully, but these errors were encountered:
Great you're interested, @timokleemann – I'm really happy if someone else also finds this feature helpful (and probably will use and test it) :)
Technically I think I got everything working by now and hopefully I can do some more tests later, so I can publish a new stable release candidate this weekend.
Here's a little preview of what's coming with this latest update:
When clients decide to add additional languages after the initial launch of a website the current logic of this extension only allows them to see/use/edit the new language in the backend, but it is not possible to show it in the frontend without making it accessible to the public.
For smaller websites this might be no big deal, but for larger projects, that take time to translate and fill in all the content for a new language, this is far from perfect – so the wish to temporarily mark languages as 'restricted' and thus make them accessible to logged-in authors in the frontend without involving them in any routing/redirecting-logic for public users popped up quite a few times in the past and I finally decided to implent this, as two cleints actively require this feature.
Might take this as an opportunity to also finish the documentation and finally publish version 2.0.0 of this extension 😶
The text was updated successfully, but these errors were encountered: