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
I have a multilingual website (in french and english). I want my blog.liquid page to be in english only. So I don't create the blog.fr.liquid page. But whenever I sync my website from production, it automatically creates me a blog.fr.liquid page. So the next time I push, I have a blog.fr.liquid page in production. The same goes for content_type_template pages.
A solution to that problem could be to make the "Published" property localized. The same goes for the content types: It would be great if the "Visible" property was localized.
The text was updated successfully, but these errors were encountered:
Just ran into this. This is an essential feature for multi-language sites.
Publish and listed fields for pages and content types must be localized so content between language versions can be different.
Right now the language versions need to be exactly the same. You can hide pages in different language versions by not showing them in a custom menu(Section) but they are still listed in the generated sitemap file.
Also it is very confusing for editors to be able to localize the title and slug in the same interface but the Published and Listed in the Menu switches are global. There is no indication of this behaviour until you try it.
Is there any special reason why this was not implemented yet? It seems like a necessary and powerful feature.
I have a multilingual website (in french and english). I want my
blog.liquid
page to be in english only. So I don't create theblog.fr.liquid
page. But whenever I sync my website from production, it automatically creates me ablog.fr.liquid
page. So the next time I push, I have ablog.fr.liquid
page in production. The same goes for content_type_template pages.A solution to that problem could be to make the "Published" property localized. The same goes for the content types: It would be great if the "Visible" property was localized.
The text was updated successfully, but these errors were encountered: