?
avatar wojsmol
wojsmol
10 May 2017

Steps to reproduce the issue

  1. Delete Super User group from Special view lewel and click Save & Close.
  2. Add public $root_user='SU_LOGIN'; to configuration.php
  3. Try add Super User group to Special view level using backend.

Expected result

Super User group successfully added to Special view level.

Actual result

No admin menu and toobar buttons

System information (as much as possible)

Joomla! 3.7.0 and staging on php 5.6.x

Additional comments

avatar wojsmol wojsmol - open - 10 May 2017
avatar joomla-cms-bot joomla-cms-bot - change - 10 May 2017
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 10 May 2017
avatar wojsmol wojsmol - edited - 10 May 2017
avatar joomla-cms-bot joomla-cms-bot - change - 11 May 2017
The description was changed
avatar joomla-cms-bot joomla-cms-bot - edited - 11 May 2017
avatar franz-wohlkoenig franz-wohlkoenig - change - 11 May 2017
Category Administration com_users
avatar wojsmol
wojsmol - comment - 11 May 2017

cc @izharaazmi as this is parly related to menu system

avatar zero-24
zero-24 - comment - 11 May 2017

Hmm you should be able to see it unsing the direct link correct? If yes you can add the view level back and fix the module display. Btw you dond need root user imo as you have a working superuser anyway ;) you can also do all that stuff via the database ;)

avatar wojsmol
wojsmol - comment - 12 May 2017

Direct links work, this is true, and you can reach the edit view of a specific view level, but there are no buttons for Save & Close. Of course, you can solve this problem through the database, which is not a problem for me, but as a moderator of the Polish Joomla forum I have found users who make queries to the database is no so easy. Then the opportunity to use $root_user made it easier to solve the problem.

avatar joomla-cms-bot joomla-cms-bot - change - 12 May 2017
The description was changed
avatar joomla-cms-bot joomla-cms-bot - edited - 12 May 2017
avatar franz-wohlkoenig franz-wohlkoenig - change - 12 May 2017
Status New Discussion
avatar zero-24
zero-24 - comment - 12 May 2017

Then the opportunity to use $root_user made it easier to solve the problem.

Sure but the problem here is $root_user are just a way to make a other user temporary super user. This is not a system recovery mode ;).

avatar brianteeman
brianteeman - comment - 12 May 2017

Sure but the problem here is $root_user are just a way to make a other user temporary super user. This is not a system recovery mode ;).

Thats exactly what it is. At the absolute minimum they should have accerss to com_users

avatar izharaazmi
izharaazmi - comment - 12 May 2017

This is happening because of the authorisedViewLevels = empty or
insufficient for that user. As of now \JAccess::getAuthorisedViewLevels
does not account to the root_user setting and hence the issue. I can do the
PR but there are few other points to worry about. Let me know.

avatar wojsmol
wojsmol - comment - 12 May 2017

PR will be welcome IMHO. Looking from the perspective of a person helping other inexperienced users.

avatar izharaazmi
izharaazmi - comment - 12 May 2017

Check the PR

avatar wojsmol wojsmol - edited - 14 May 2017
avatar brianteeman
brianteeman - comment - 14 May 2017

closed see #15988

avatar brianteeman brianteeman - change - 14 May 2017
The description was changed
Status Discussion Closed
Closed_Date 0000-00-00 00:00:00 2017-05-14 11:02:12
Closed_By brianteeman
avatar brianteeman brianteeman - close - 14 May 2017

Add a Comment

Login with GitHub to post a comment