Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

publishing per tranlsation #70

Closed
bashu opened this issue May 13, 2015 · 1 comment
Closed

publishing per tranlsation #70

bashu opened this issue May 13, 2015 · 1 comment

Comments

@bashu
Copy link
Member

@bashu bashu commented May 13, 2015

right now if you publish for example English translation, then all other will be counted as published and vice verse, is it possible to fix? where to start?

@vdboor
Copy link
Contributor

@vdboor vdboor commented May 13, 2015

Yes that would be possible.

This was done in the past to make it easy to query for published pages (plus the cms didn't have translations at first). In my experience, things get really complex when each translation has it's own published status. However I'm eager to have a good solution for this.

The biggest issue is likely, can you still query all pages that are published (e.g. to display in a menu), because you need to fetch both the pages with a published fallback or published translation.

An advanced addition to this would be a versioning system where you can preview changes first, and then publish them.

@bashu bashu closed this Oct 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants