@wendellcrain well, as its name says, the User Tools widget offers links to functionalities that only logged in people are supposed to get access to. Please, tell us if you expect a different behavior on this widget or if maybe I misunderstood your question.

Regarding the skin files edition, you are still able to browse and edit the skin files through the File Manager being logged in as admin.

Please get back to us if you remain getting troubles with this.

Regards!

It could be me just not understanding how to set this up. Here are a couple screen shots from the current system running 2.4.6:

But then after the 5.0.8 upgrade on a test system, the "User Tools" box disappears unless you are logged in. Then if you enter the URL, log in as admin, I cannot find the skins folder under the File Manager.

Thanks in advance for your help!

All right, thanks for the screenshots.

As I said before, the links included in the User Tools widget are meant to be presented to logged in users. The links to Login, Register or Admin are not anymore included in this widget. They have been relocated to other places in the site, i.e.: the main menu includes a Log in link by default. If you want to get more information about it, please go to this page: http://b2evolution.net/man/back-office-reference/managing-collections/widget-settings/widgets/user-tools-widget.

About the skins folders, the File Manager has a setting to let you enable / disable the access to specific file roots. Please, read this page for more details: http://b2evolution.net/man/back-office-reference/managing-files/file-manager-settings/accessible-file-roots

Regards!

Manuel-Thanks! That helped about the User Tools. I added the Login widget and that would be back to normal.

About the skins folder-I already had the Skins folder checked to be enabled. I then tried to uncheck it and re-check it again without a change. I verified permissions and user/group ownership.

I do realize that I can use FTP to access the directory, but I have several other users that are tech-challenged and would function better with a web interface. Any other suggestions on where to look for a block to this?

Thanks again!

Well, I still have not found what setting is keeping me from being able to get to the skins directory. Spent some time looking at the code and found a hack that would allow the admin user to access the skins directory. It is in "_fileroot.class.php":

function FileRoot( $root_type, $root_in_type_ID, $create = true )
{
<<SKIP SOME CODE>>
    case 'skins':
        if( ! $Settings->get( 'fm_enable_roots_skins' ) )
        { // Skins root is disabled:
                $Debuglog->add( 'Attempt to access skins dir, but this feature is globally disabled', 'files' );
        }
         elseif( empty( $current_User ) || ( ! $current_User->check_perm( 'templates' ) && $current_User->ID <> 1 ) )
        { // No perm to access templates:
                $Debuglog->add( 'Attempt to access skins dir, but no permission', 'files' );
        }
        else

Adding the "&& $current_User->ID <> 1" skips the permission check for the administrator. Not exactly what I would like to to do. I am concerned as to what else me upgrading this has broken that I have not found yet. By-the-way, this is the first custom coding added to the site other than the skin.

If anyone can give me a place to look as to why the user perms, group perms, or file settings are not working I would appreciate it greatly.