[#42254] - [4.4] Access level registered for mod_user
- Pending
- Medium
- Build: 4.4-dev
- # 42254
- Diff
- chmst:atum-logout
User tests: Successful: Unsuccessful:
Pull Request for Issue #28804 .
Summary of Changes
Remove rendering status modules from login, Set accesslevel "registered" for mod menu
Testing Instructions
Grant access to the backend for a usergroup which has not viewlevel "special", for example to usergroup registered.
The user then can login to the backend.
Actual result BEFORE applying this Pull Request
He cannot log out
Expected result AFTER applying this Pull Request
Set access-level for mod_user to "registered" or make a fresh installation for a new test.
mod_user is active, the user can log out.
Link to documentations
Please select:
-
Documentation link for docs.joomla.org:
-
No documentation changes for docs.joomla.org needed
-
Pull Request link for manual.joomla.org:
-
No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | SQL Administration com_admin Postgresql Templates (admin) Installation |
| Labels |
Added:
PR-4.4-dev
|
||
| Title |
|
||||||
I think we can't hard code access level ids in sql statements (there is no guarantee that 2 === registered)
Should not be enough for this module to appear that the user have access to the administrator? How I see it, this module do not need to proccess any access level to see if he can or not show up in that position. If you log in, you need a way to log out and you don't need an access level to define it.
| Title |
|
||||||
Is it intended top remove the link to the frontend of the site from the login page?