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

Always show post content switch #112

Closed
herrvigg opened this issue Jun 21, 2018 · 3 comments
Closed

Always show post content switch #112

herrvigg opened this issue Jun 21, 2018 · 3 comments
Labels
legacy PR Legacy PR imported from original repo

Comments

@herrvigg
Copy link
Collaborator

herrvigg commented Jun 21, 2018

Issue by spartacus-zeus
Wednesday Apr 01, 2015 at 21:26 GMT
Originally opened as qTranslate-Team/qtranslate-x#112


This implements the possibility to always show the content of a post, even if the desired language is not available. The content will be shown in the default language of the site and if that is not available it will use the first available one.

This pull request does however not yet implement the back-end switch for admins. This means that the 'always_show_content' boolean will have to be set in a child theme for the time being.

Partly fixes #21

Happy to hear your feedback!


spartacus-zeus included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/112/commits

@herrvigg herrvigg added bug Something isn't working, reproducible legacy issue Legacy issue imported from original repo labels Jun 21, 2018
@herrvigg herrvigg changed the title Categorie Names containing an apostrophe break Always show post content switch Jun 23, 2018
@herrvigg herrvigg reopened this Jun 23, 2018
@herrvigg herrvigg added legacy PR Legacy PR imported from original repo and removed bug Something isn't working, reproducible legacy issue Legacy issue imported from original repo labels Jun 23, 2018
@herrvigg
Copy link
Collaborator Author

Comment by johnclause
Wednesday Apr 01, 2015 at 21:47 GMT


Cannot you do it without removing dots? Change the logic a little bit? I am hesitant to ask thousands of users to adjust their settings to remove dot, which are now stored in their databases. Besides some languages would not use dot in such case.

@herrvigg
Copy link
Collaborator Author

Comment by spartacus-zeus
Wednesday Apr 01, 2015 at 22:19 GMT


Agreed, these commits should solve it!

@herrvigg
Copy link
Collaborator Author

Comment by johnclause
Wednesday Apr 01, 2015 at 22:56 GMT


I will pull it in later, I have to finish something first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
legacy PR Legacy PR imported from original repo
Projects
None yet
Development

No branches or pull requests

1 participant