This repository was archived by the owner on Jan 25, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Jan 25, 2021. It is now read-only.
Blog Sample Data #202
Description
I would have reported this in the main repo but as the plugin is being worked on here it seemed best to report here
The permissions on the menu items created in the sample data need to be reviewed
- Author Login (guest)
- Template Settings (super user)
- Author Login alias in footer (guest)
The Logout menu item should be using the specific logout menu type
Activity
richard67 commentedon Oct 25, 2020
@chmst That's something for you. I help of course if I can.
chmst commentedon Oct 26, 2020
Changing the view level of menu item "Author Login" to "guest" needs changing the installation file (base.sql). Otherwise it results in a 403 (as the logout button does already).
Template Settings are view Level "special" - we don't have a viel level for super users only.
But this remembers that the name "Author Login" is not correct. I change it to "Login".
richard67 commentedon Oct 26, 2020
@chmst Changing base.sql and maybe even making an update SQL script to change installation on update would not be a big thing, I think. But the question is: Are we allowed to do that regarding the restrictions for database changes in the mission or task of our Cassiopeia enhancement project? If you think we can do it, I can make a PR to change that view level.
chmst commentedon Oct 27, 2020
Changing the sql script It is a bigger change because there are also multilingual and testing sample data who use the installed modules. If we do that, it must be planned carefully - and as @brianteeman says, it is more an issue for joomla-cms.