Support

Akeeba Backup for Joomla!

#8687 Permission Warning on media/com_akeeba in version 3.1.1

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Tuesday, 09 November 2010 20:24 CST

user18602
Upgraded from 3.1 to 3.1.1 and now get the large yellow warning below.

ALL APPEARS TO WORK DESPITE THE WARNING

Note: I do have the right permissions but we are running in FastCGI mode. Never had this on the previous version.


WARNING



Akeeba Backup could not determine the permissions of the media/com_akeeba directory.



Please do one of the following:



1. Activate Joomla!'s FTP mode in Global Configuration

2. Change the permissions of the media/com_akeeba directory and all of its subdirectories to 0755 and all of its files to 0644 using your FTP client.



Akeeba Backup will most likely not work at all if you do not perform these steps. Do not ask for support if you can see this message. All the information you need is already on this message.

dlb
This appears to be a cosmetic issue with the way the screen is built and displayed in 3.1.1 stable. On my slower machine, I can see the error message display and clear, on my faster machine, I can't see the error message at all on the same sites.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

bervin
I don't usually add posts that say "Me too!", but the big yellow warning box with red letters is so annoying that I have to chime in. There is no profit in annoying your paying customers.

My file permissions are correct and backups run flawlessly as usual, so please modify the warning box. I can't demonstrate Akeeba backup for my customer's if it displays a huge, ugly warning box all the time.

bervin
Additional note - On my system it appears that Akeeba Backup is changing the permissions on the files in the media/com_akeeba directory to 755.

user6102
If I have changed the permission like the message asks, why does it not go away?
I have had the same permissions for a year with no trouble, why all of a sudden is it angry now?

nicholas
Akeeba Staff
Manager
It looks like that Javascript is taking MUCH longer to load than I anticipated on some servers. I am going to remove that message and post a 3.1.2 version in a couple of hours.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user18602
Thanks.. the message was just v.large :cool:

bervin
I've installed version 3.1.2 and it works perfectly, with no error message.

Excellent work. Thank you!

nicholas
Akeeba Staff
Manager
You're welcome and sorry for the mess up (it seems I had ultimately forgotten to add a single line of Javascript code!)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user11267
I installed 3.1.2 and I'm still receiving the warning messages below. Does this mean these particular files aren't getting backed up?



Unreadable file E:/folder/folder/templates/rt_quantive_j15/images/menus. Check permissions
Unreadable file E:/folder/folder/templates/rt_quantive_j15/images/logo. Check permissions
Unreadable file E:/folder/folder/templates/rt_quantive_j15/images/body. Check permissions
Unreadable file E:/folder/folder/templates/rt_quantive_j15/images/backgrounds. Check permissions
Unreadable file E:/folder/folder/templates/rt_quantive_j15/images/backgrounds/style8. Check permissions
Unreadable file E:/folder/folder/templates/rt_quantive_j15/images/backgrounds/style7. Check permissions
Unreadable file E:/folder/folder/templates/rt_quantive_j15/images/backgrounds/style6. Check permissions
Unreadable file E:/folder/folder/templates/rt_quantive_j15/images/backgrounds/style5. Check permissions
Unreadable file E:/folder/folder/templates/rt_quantive_j15/images/backgrounds/style4. Check permissions
Unreadable file E:/folder/folder/templates/rt_quantive_j15/images/backgrounds/style3. Check permissions
Unreadable file E:/folder/folder/templates/rt_quantive_j15/images/backgrounds/style2. Check permissions
Unreadable file E:/folder/folder/templates/rt_quantive_j15/images/backgrounds/style1. Check permissions
Unreadable file E:/folder/folder/templates/rt_quantive_j15/html/mod_roknavmenu/themes. Check permissions
Unreadable file E:/folder/folder/templates/rt_quantive_j15/html/com_k2. Check permissions
Unreadable file E:/folder/folder/templates/rt_quantive_j15/html/com_contact. Check permissions
Unreadable file E:/folder/folder/rokdownloads. Check permissions
Unreadable file E:/folder/folder/rokdownloads/VisiNet Command. Check permissions
Unreadable file E:/folder/folder/rokdownloads/Tech Tips. Check permissions
Unreadable file E:/folder/folder/plugins/system/Zend/Tool. Check permissions
Unreadable file E:/folder/folder/plugins/system/Zend/Tool/Framework/Client/Response. Check permissions
Unreadable file E:/folder/folder/plugins/system/Zend/Mail/Protocol/Smtp. Check permissions
Unreadable file E:/folder/folder/plugins/system/Zend/Auth/Adapter/Http. Check permissions
Unreadable file E:/folder/folder/plugins/system/rokbox/themes. Check permissions
Unreadable file E:/folder/folder/plugins/system/forcepasswordchange. Check permissions
Unreadable file E:/folder/folder/plugins/system/forcepasswordchange/assets. Check permissions
Unreadable file E:/folder/folder/plugins/content/jw_sigpro/templates. Check permissions
Unreadable file E:/folder/folder/plugins/content/jw_sigpro/popup_engines/jquery_prettyphoto/images/prettyPhoto. Check permissions
Unreadable file E:/folder/folder/plugins/content/jw_allvideos. Check permissions
Unreadable file E:/folder/folder/modules/mod_roknewspager/themes. Check permissions
Unreadable file E:/folder/folder/modules/mod_rokajaxsearch/themes. Check permissions
Unreadable file E:/folder/folder/modules/mod_k2_users/tmpl. Check permissions
Unreadable file E:/folder/folder/modules/mod_k2_content/tmpl. Check permissions
Unreadable file E:/folder/folder/media/k2. Check permissions
Unreadable file E:/folder/folder/media/com_juga. Check permissions
Unreadable file E:/folder/folder/media/com_akeeba. Check permissions
Unreadable file E:/folder/folder/media/com_akeeba/plugins. Check permissions
Unreadable file E:/folder/folder/media/com_admintools. Check permissions
Unreadable file E:/folder/folder/images/photos. Check permissions
Unreadable file E:/folder/folder/images/originalphotos. Check permissions
Unreadable file E:/folder/folder/images/comprofiler. Check permissions
Unreadable file E:/folder/folder/images/avatar. Check permissions
Unreadable file E:/folder/folder/components/com_toolbareditor. Check permissions
Unreadable file E:/folder/folder/components/com_sql2excel/helpers/PEAR/Spreadsheet. Check permissions
Unreadable file E:/folder/folder/components/com_sql2excel/helpers/PEAR/Spreadsheet/Excel. Check permissions
Unreadable file E:/folder/folder/components/com_akeeba/views. Check permissions
Unreadable file E:/folder/folder/aspnet_client. Check permissions
Unreadable file E:/folder/folder/aspnet_client/system_web. Check permissions
Unreadable file E:/folder/folder/aspnet_client/system_web/4_0_30319. Check permissions
Unreadable file E:/folder/folder/administrator/templates/khepri/html/com_menus. Check permissions
Unreadable file E:/folder/folder/administrator/components/com_sql2excel/views. Check permissions
Unreadable file E:/folder/folder/administrator/components/com_akeeba/plugins. Check permissions
Unreadable file E:/folder/folder/administrator/components/com_akeeba/language. Check permissions
Unreadable file E:/folder/folder/administrator/components/com_akeeba/assets. Check permissions

nicholas
Akeeba Staff
Manager
Yes, this means that the aforementioned files do not have sufficient read permissions. A simple way to make them readable is installing our free Admin Tools Core component and using the "Fix Permissions" feature to reset all directory permissions to 0755 and all file permissions to 0644. This will allow all of them to be backed up. If you need to have some directories or files with different permissions no worries, Admin Tools Core can be set up with customized permissions for any directory or file you may want to use.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user11267
Thanks for the reply.

I'm actually already using Admin Tools Pro, and I ran the fix permissions tool again just to make sure. I still received those errors. When I looked in Permissions Configuration, I noticed that almost all the folders are listed as being 777 and files are 666. If I use the drop-down menu to change the folder permissions to 755 and click 'save custom permissions', it tells me "The custom permissions have been saved" but still lists them as being 777.

Shouldn't it be re-listing it as 755 if it was working correctly?

nicholas
Akeeba Staff
Manager
After saving the permissions you have to go back to the Control Panel and click on Fix Permissions to apply the settings. The Custom Permissions page only sets up the permissions, it doesn't apply them. You may also need to enable the FTP settings in your Global Configuration for the permissions of all files and directories to be applied, as mentioned in our documentation ;)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user11267
Hmm, well I set the global FTP up correctly but I'm still seeing permissions of 777 and 666.

user11267
I also applied the 'fix permissions' tool after I had set the folders to 755, and they still read 777.

nicholas
Akeeba Staff
Manager
Is the FTP Root parameter blank? It shouldn't be blank. It should be the FTP path to your site's root. You can check it with FileZilla. If it's blank I am sure that the FTP mode doesn't work correctly and this is why permissions don't get applied.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user14940
Perhaps this is slightly out of topic as I have tried ver. 3.1.2 on a win 2008 Server (wamp) but I also got some unreadable folder warnings. I also tried the fix permissions tool, without success. Ultimately, I uninstalled ver 3.1.2 and installed again ver 3.1. The backup process now dos not produce any warnings.

kuk
I have the same issue since I have installed v3.1.2 but my CMS runs under Windows (!) - UNIX permission checks makes here no sense. The Windows permissions are ok. Looks your tool for UNIX permissions or do it recognize that it runs under Windows?

I want to be sure that my backups are ok.

nicholas
Akeeba Staff
Manager
@gd047 Akeeba Backup 3.1 has a bug. It doesn't display the warnings, which is completely different than saying that it takes a full backup. Just because you don't see the problem it doesn't mean it's not there ;) In fact, on Windows servers you do not have permissions, you have ACLs. If you have remote access to the server, right-click on the web root of your site, click on Properties and go to the Security tab. In there you can allow the Full Access privilege to the Everybody user and apply the change recursively. This should do the trick.

@kuk Same as my reply to gd047. Moreover, the best way to test your backups is to, well, restore them on the same or a different server. If the site works properly after the restoration, you have a good backup. As simple as that.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

kuk
Sorry, what I wanted to know is what kind of permissions Akkeba checks: UNIX rights only? I think so because your 'Admin Tool' can this only. But I don't know this exactly. Your tip to give access to 'Everybody' could not be your serious. Doing this will break each security for a windows server.

But what are the consequences for these warnings? That Akkeba do not backup these files? If so why it works before? Better to downgrade?

user19427
I just installed 3.1.2. I keep getting warnings like the following-

Unreadable file /administrator/components/com_breezingforms/libraries/jquery/themes. Check permissions

This is on a Windows Server 2003. I checked the permissions and they are correct. I checked a number of the errors that it reported and noticed one thing in common.. All the errors were about folders. Each of those folders did not have any files, a number of them did have sub-folders. It looks like the application is complaining if it finds a folder without any actual files.

nicholas
Akeeba Staff
Manager
@kuk Is it a live server? If so, give Read access to all files for the user under which your server is running. I somehow assumed we were talking about a local Windows server.

@abernfr Thanks, I will investigate further

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user11267
@nicholas I actually had the root path there, but I added it again and tried changing permissions again, still got the same errors. I'm actually using a windows machine for this site, and took note of your responses below. I didn't have an "everyone" user, so I added that user to the root, applied full access, and still encountered the unreadable errors. I checked that the permissions for 'everyone' had propagated recursively, and indeed they had. At that point, I tried setting full access permissions for iusr, verified they had been applied recursively, and tried the backup again...still got the unreadable errors.

kuk
It`s a live Windows 2003 server and the permission settings are ok. WIN/IIS needs the internal IUSR_machinename for web sites and it has read/wright rights where necessary. The system runs since 3 years without problems and I use Joomlapack/Akeeba for a long time and had never before these issues. So only thing what has changed is 'Akeeba backup' - no need to play around at my permissions. So again: what do the Akeeba backup when it assumes a permission problem? What has changed against former versions (with not such problems)? Do I can trust the backup?

nicholas
Akeeba Staff
Manager
Can you verify that the warnings appear only for empty directories (directories without files)? I think this is the problem and it's only a cosmetic one, i.e. the backup is successful and you can confirm it by restoring the site to a local server. It also seems to affect only Windows-based servers, no matter the server software (Apache or IIS) they are using. If you guys can confirm that pattern I observe here I'll be able to fix it very fast. :) Thank you!

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user14940
No, the message appears for directories that also have contents, i.e. \administrator\components\com_akeeba\akeeba\engines However, as far as I can see, the contents of those directories were actually backed up. Indeed, the message appears for empty directories too. Those directories are NOT backed up (the restored site does not contain those empty -yet needed- directories). I guess that this is a not exactly a cosmetic problem. Anyway, please reply to this message when there is a fix available and I'll be happy to test it and give you feedback.

Thanks
G.D.

kuk
I checked the warning list (and it is a very long list) and it seems that permission warnings accurs for directories which are indeed empty or have subdirectories inside without a file/s in the directory itself.

I will do a restore today and then inform you what happens.

steph.s
Hey Kuk,
That sounds great, let us know how it goes.

user11267
I just attempted a backup and restore. The backup threw the same errors as before, and completed successfully after about 45 minutes. When I went to restore the site on my local machine with kickstart 3.1.5, it threw the error message...

"An error occured
INVALID_FILE_HEADER"

nicholas
Akeeba Staff
Manager
A fixed version is just posted in the Developer's Release area. Please use this one to take a new backup. It should complete without those warnings. Also, when downloading the file, please use Firefox or Chrome or —even better— use FTP in Binary transfer mode to rule out transmission errors. Finally, please use Kickstart 3.1.5 or the latest version of Akeeba eXtract Wizard to extract the archive locally.

I appreciate your feedback and patience :)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user11267
Doing a new backup now, and will do a test restore when its finished. I'll let you know the status when its complete.
Thanks for the quick response.

kuk
Ok, I did my tests:
1. Make a backup on Windows live system with Akeeba Pro 3.1.2 - warnings are reported
2. Transfered the file to my test system (WIN 7/IIS 7.5) and restored it (with kickstart 3.1.5) - runs perfectly, no errors.
3. Make some random checks - site works.
4. Installed the developper version (svn289) on test system - make a backup - no warnings any more.
5. Restored the site - no problems.
6. Did random checks again - no problems.
7. Make a folder/file comparison between the 2 sites - are equal, no missing files.

So, I think everything is ok.

Thank you :)

nicholas
Akeeba Staff
Manager
Splendid! Some more minor things to do and I'll release a new version very soon :)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user11267
I concur with Kuk's test results. I ran a new backup with the developer patch from yesterday, and was able to restore the site completely with no errors. Thanks again for the quick response.

nicholas
Akeeba Staff
Manager
Thank you very much, both of you! I will move this release to general availability (official release) status today.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!