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
[3.6.0 Alpha1] fix language access inconsistency #10646
Conversation
Won't this mean that if a language has been set to anything other than public it will be changed on an update. |
I have already considered that this access field can be changed. That's why I made a restriction: |
i think it would be better to have that change in new sql files. Also since a user can easily change the language title, wouldn't be better to change all languages that have access level of '0'? (there is no access level with 0 id) UPDATE `#__languages` SET `access` = 1 WHERE `access` = 0; Even then, a issue that remains is if the user somehow deleted the view access level with the id 1 (Public). Probably that's a really wild scenario since for deleting the Public access level you need to have no content with Public access level. |
Isn't that a known issue for updated sites and you actually should have a post-install message about it? Setting it to 1 isn't the correct thing to do. The access level with the id 1 can be anything. It just happens to be "public" on most sites because it's preinstalled this way, but you can change that. |
See https://github.com/joomla/joomla-cms/blob/staging/administrator/components/com_admin/postinstall/languageaccess340.php for the relevant postinstall code. |
yeah, @Bakual is right IMO. |
I knew there was a message just couldn't find it. Thanks
|
I'm closing this as a known issue which will not be fixed. |
also, we prvented an error in the languagefilter. see #6194 |
One more inconsistency between updated Joomla site and freshly installed Joomla site.
Testing Instructions
Expected result
We must see Access: Public (as in freshly installed Joomla 3.6.0).
Actual result
But we see Access: not set
This PR fixes this inconsistency for English language access field.
Exploring the problem I discovered when this inconsistency was made #2714