Support

Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? 
Have I searched the tickets before posting? YES
Have I read the documentation before posting (which pages?)? YES
Joomla! version: (2.5.8)
PHP version: (unknown)
MySQL version: (unknown)
Host: (Siteground)
Akeeba Backup version: (3.6.12 PRO)

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue:

I created a new user group (backup manager) and gave that group permission to login to backend as well as "Allow" every permission for Akeeba Backup.  I assigned a user (who is not an admin) to this new group.  I logged in as that user.  While the user can see the Akeeba control panel, the user sees no input area after clicking on "Backup" (i.e., it is as if the view does not display).  I checked with ACL Manager, and it shows that this user should have full access to the component.

However, if I give the user global rights to edit, then that user can see the Backup screen.  Of course, the expectations are that access to a component should require only permissions set on the component and not the need to Allow global permissions.

Nicholas,

The one thing different you did was to assign the user also to Manager (which provides permission for logging in to the admin) whereas I have my new group includes that permission (admin login).  Actually, I create a group called "backend access" that does nothing by grant the right to login to the backend, and then my role-based groups each inherit from this group, picking up the permission for admin login.

So in your approach, the manager group adds the global permission to edit, whereas in mine (trying to follow least permissions), the only permissions granted are those provided by the component plus admin login.

I know I'm not alone in this approach or one similar.  Sander recommends removing almost all of the groups (but retaining Super and Registered) and add in groups as needed - meaning Manager and Administrator are no longer available - and that means global permissions are selectively granted and only if needed.

So I think the cause of my blank view is that I'm taking an approach that does not grant Edit globally, and somewhere the code that displays the view for the backup screen is checking that global permission.

[Additional info: this was from an established 2.5.x site with standard Akeeba backup.  The site is now at 2.5.8 and I had just upgraded Akeeba Backup to Pro.] 

I also thought it might be viewing access (access level).  I added the new group to Special, but that did not help.

And I thought perhaps the backup process did require some global permissions - somewhere within all the "magic" it does.  Thanks for looking into it.  It sure would be nice to be able to give a user just the permission to run a backup.

Nicholas,

I installed this new version on top of the old.  While it installed successfully, it reported a sizable list of your fof library files that it could not delete.

But that install now allows my test user to get access to the backup screen.  So this seems to have fixed what I was looking for.  Many thanks.

When do you expect to have this into a Stable release?  I'm asking just asking in case my client wants to know when I can get her access to the backup feature.

OK.  If you feel the dev version is essentially stable, that's good enough for me.  Again, thanks for the fix.