Description of my issue:
I have been using Akeeba successfully on this site running Joomla 3.1.6. I recently upgraded to Joomla 3.2.0 and had a few issues. Primary issue was lack of access to Joomla administrator control panel. I was able to apply the database fix. Other resolved issues included fix of system email and new user front end login. However, Akeeba backup runs and appears to have completed, but is showing> Unreadable directory C:\HostingSpaces\xxxxxx\xxxxxx\wwwroot. Fixes I have attempted are requesting my host (Windows Server) to reset permissions, disabling all third party extensions, including Akeeba, refreshing Akeeba settings, re-installing Akeeba Backup 3.8.2 and installing Admin Tools which shows
Warning: PHP reports an empty path as the base directory of your site. This is caused by a bug in older versions of PHP. Please tell your host to upgrade the installed PHP version on their server. If you try using the Fix Permissions button it is very possible that you will be locked out of your site.
As Akeeba backup was working prior to the installation, I assume the unreadable message in backup and the warning in in Admin Tool are related. As the server PHP 5.3 was working prior to to the Joomla upgrade, I am hesitant to ask them to upgrade without consulting you. I've noted several posts on the Joomla forum relating Joomla upgrade problems with Akeeba re: FOF, .htaccess. Other Joomla users that are not Akeeba users have reported both back end and front end problems. I've noted fixes in the trouble shooter guide regarding deleting library files. I did not locate any forum users with the unreadable root problem. As the backup was working fine before the Joomla upgrade, and the log now shows:
[131118 09:00:05] PHP WARNING on line 122 in file <root>\administrator\components\com_akeeba\akeeba\drivers\mysql.php:
[131118 09:00:05] mysql_close(): 49 is not a valid MySQL-Link resource
and as there seem to be a number of possible fixes, are you able to provide the correct steps to solve this issue.
Email to host is below and copy of log is attached.
Thank you!
roryman
-----Original Message-----
From: [email protected]
Sent: Sunday, November 17, 2013 1:40 AM
To: xxxxx
Subject: Re: [#JEV-96624-342] Akeeba Backup / Joomla 3.2
Hello,
We have updated permission of C:\HostingSpaces\xxxxxx\xxxxxx.net\wwwroot. please try it again.
Please tell us if you have any questions. thanks!
=======================================================
Support Team
On Sat, 16 Nov 2013 22:49:01 Central Standard Time,
>
> I recently ran the upgrade from Joomla 3.1.5 to Joomla 3.2.0. Upgrade crippled back end admin login and had to apply database fix in Joomla.
>
> http://www.cloudaccess.net/about-us/blog/entry/2013/11/13/upgrading-from-joomla-3-1-to-3-2-problems-workarounds.html
>
> The fix seems to have worked except for my backup component Akeeba Backup. Screenshot attached.
>
> Got this message
>
> Unreadable directory C:\HostingSpaces\xxxxxx\xxxxxx\wwwroot
>
> Akeeba Backup was working fine before the upgrade to Joomla 3.2 I upgraded to pro version of Akeeba and got same error. The backup does finish, but it is not backing up the root directory files. My previous backups were about 28MB and now only 986kb. I'm also attaching a copy of the backup log.
>
> https://www.akeebabackup.com/documentation/troubleshooter/abunreadablewarnings.html
>
> Would you please check and see if the <opendir> settings changed?
>
> Akeeba notes:If you get that kind of warning for <root>, it means that your site's root is not readable. This will cause Akeeba Backup to be unable to backup your site. In this case, using your favourite FTP application, connect to your site and look for your site's web root. It is usually a directory named public_html, httpdocs, htdocs, www or something like that. If unsure, ask your host. Change its permissions to 0755. If you can not do that yourself, ask your host to do that for you. If they refuse on the grounds of security, explain to them that a. it is necessary to backup your site and b. they are probably doing something wrong if other users are allowed to browse your site's files (and swiftly change to a more secure host!).
>
> If you are on a Windows server, there is no notion of permissions. Instead, you have to edit the Windows ACLs to allow PHP to be able to list the contents of your site's directories. Since this procedure is highly dependent on the server setup, please ask your host to do it for you.
>
>
>
>
>
>
I have been using Akeeba successfully on this site running Joomla 3.1.6. I recently upgraded to Joomla 3.2.0 and had a few issues. Primary issue was lack of access to Joomla administrator control panel. I was able to apply the database fix. Other resolved issues included fix of system email and new user front end login. However, Akeeba backup runs and appears to have completed, but is showing> Unreadable directory C:\HostingSpaces\xxxxxx\xxxxxx\wwwroot. Fixes I have attempted are requesting my host (Windows Server) to reset permissions, disabling all third party extensions, including Akeeba, refreshing Akeeba settings, re-installing Akeeba Backup 3.8.2 and installing Admin Tools which shows
Warning: PHP reports an empty path as the base directory of your site. This is caused by a bug in older versions of PHP. Please tell your host to upgrade the installed PHP version on their server. If you try using the Fix Permissions button it is very possible that you will be locked out of your site.
As Akeeba backup was working prior to the installation, I assume the unreadable message in backup and the warning in in Admin Tool are related. As the server PHP 5.3 was working prior to to the Joomla upgrade, I am hesitant to ask them to upgrade without consulting you. I've noted several posts on the Joomla forum relating Joomla upgrade problems with Akeeba re: FOF, .htaccess. Other Joomla users that are not Akeeba users have reported both back end and front end problems. I've noted fixes in the trouble shooter guide regarding deleting library files. I did not locate any forum users with the unreadable root problem. As the backup was working fine before the Joomla upgrade, and the log now shows:
[131118 09:00:05] PHP WARNING on line 122 in file <root>\administrator\components\com_akeeba\akeeba\drivers\mysql.php:
[131118 09:00:05] mysql_close(): 49 is not a valid MySQL-Link resource
and as there seem to be a number of possible fixes, are you able to provide the correct steps to solve this issue.
Email to host is below and copy of log is attached.
Thank you!
roryman
-----Original Message-----
From: [email protected]
Sent: Sunday, November 17, 2013 1:40 AM
To: xxxxx
Subject: Re: [#JEV-96624-342] Akeeba Backup / Joomla 3.2
Hello,
We have updated permission of C:\HostingSpaces\xxxxxx\xxxxxx.net\wwwroot. please try it again.
Please tell us if you have any questions. thanks!
=======================================================
Support Team
On Sat, 16 Nov 2013 22:49:01 Central Standard Time,
>
> I recently ran the upgrade from Joomla 3.1.5 to Joomla 3.2.0. Upgrade crippled back end admin login and had to apply database fix in Joomla.
>
> http://www.cloudaccess.net/about-us/blog/entry/2013/11/13/upgrading-from-joomla-3-1-to-3-2-problems-workarounds.html
>
> The fix seems to have worked except for my backup component Akeeba Backup. Screenshot attached.
>
> Got this message
>
> Unreadable directory C:\HostingSpaces\xxxxxx\xxxxxx\wwwroot
>
> Akeeba Backup was working fine before the upgrade to Joomla 3.2 I upgraded to pro version of Akeeba and got same error. The backup does finish, but it is not backing up the root directory files. My previous backups were about 28MB and now only 986kb. I'm also attaching a copy of the backup log.
>
> https://www.akeebabackup.com/documentation/troubleshooter/abunreadablewarnings.html
>
> Would you please check and see if the <opendir> settings changed?
>
> Akeeba notes:If you get that kind of warning for <root>, it means that your site's root is not readable. This will cause Akeeba Backup to be unable to backup your site. In this case, using your favourite FTP application, connect to your site and look for your site's web root. It is usually a directory named public_html, httpdocs, htdocs, www or something like that. If unsure, ask your host. Change its permissions to 0755. If you can not do that yourself, ask your host to do that for you. If they refuse on the grounds of security, explain to them that a. it is necessary to backup your site and b. they are probably doing something wrong if other users are allowed to browse your site's files (and swiftly change to a more secure host!).
>
> If you are on a Windows server, there is no notion of permissions. Instead, you have to edit the Windows ACLs to allow PHP to be able to list the contents of your site's directories. Since this procedure is highly dependent on the server setup, please ask your host to do it for you.
>
>
>
>
>
>
