Support

Hello
Sorry it's first time I have a pb with your great extension Akeeba Backup. The problem now is for the joomla core version.

I am the superadmin and I have a user in an administrator role (default roles I don't touch users acl). All works fine untill now on our development site (but made with php 7.0 => I just see that your extension in not yet compatible)
But friday, I think, I have made all updates : joomla, akeeba and others extensions.
Now my administrator says that he can't acess to akeeba, he have an error 403 "You are not authorised to view this resource for administrator user".
So I test and check the roles for akeeba : access to akeeba = authorized, bakcup = authorized, dowload = authorized. So I think all is ok ?

Today I uninstalled akeeba and installed it again (with now php 5.6). I can make backups. But I have allways the problem for the administrator role : no access

Have you an idea?
Thanks

By default, Akeeba Backup can only be used by a Super User. If you want an Administrator to access the component, you must adjust the ACL permissions under Options in the upper right corner.

OK Dale, but my ACL permissions for the administrator is : access to akeeba = authorized, bakcup = authorized, dowload = authorized. So I think all is ok ?
It works like that before the update and after the update it doesn't work. Is something changes with the new version of Akeeba ?

ah nice ! I'll wait
Thanks

Hello

I just install the new version but the pb is always present. But in parameters I just see for my administrator rules that "configure" was on not authorised so with "authorised" it's now ok !!!

Just another thing untill my reinstatement on last friday, I just see that my backups for jpa becomes huge !
Before 26Mo and now 116 Mo and without adding huge files from this date. Have you encountered this ?
I don't think that the fact to change php7 to php 5.6 has an impact on backups ?

thanks

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.