Site Restoration

#15200 Possible permission issues post restore

Posted in ‘Site restoration’
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

PHP version
CMS Type
CMS Version
Backup Tool Version
Kickstart version

Latest post by nicholas on Wednesday, 27 February 2013 04:43 CST


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.9
PHP version: 5.3.18
MySQL version: 5.5.28
Akeeba Backup version which took the backup: 3.6.12
Kickstart version used to extract the backup: 3.6.0

Description of my issue:

I restored a site from a development area to it's live area, and I have multiple issues appearing on the live site that you might be able to guide me on.

The first issue noticed was that the Joomla Media manager failed to upload images, although it was possible to delete images.

The failure displays 2 warnings on an otherwise blank screen:

Warning: mysql_fetch_row() expects parameter 1 to be a resource, boolean given in /.../public_html/libraries/joomla/database/mysql.php on line 683

Warning: mysql_fetch_row() expects parameter 1 to be a resource, boolean given in /.../public_html/libraries/joomla/database/mysql.php on line 726

Both refer to methods refer to loading a result-set row into memory and then releasing said result-set row.

After failing to find a solution, and noting that the media manager bundled with K2 is working fine I considered reinstalling the Joomla Core (2.5.9).

Before doing this I wanted to backup and upgrade Akeeba Backup and Admin Tools currently running versions 3.6.12 and 2.4.4 respectively.

While the components continue to work I am unable to upgrade Admin Tools either via Live Update or the Extension Manager. A 403 error screen appears:

You don't have permission to access /administrator/index.php?option=com_admintools&view=liveupdate&task=install on this server

In addition when I take the site into 'Emergancy Offline' mode I get locked out of the administration area of the site until I manually replace the .htaccess file via FTP.

These sets of issue are not occurring on the development site, I have upgraded Admin Tools successfully and the original issue of the media manager is not occurring here. Both sites are within the same cpanel.

I think the above issues could be related. These issues seem like a permission problem from the restoration of the site. I have run the fix permission feature on Admin tools (files 644, directories 755), but this did not solve the upgrade issue, and the log and tmp directors are correctly configured for the live site.

If you could suggest a likely cause or course of action I would be very grateful.

I could at this stage remove the apparently corrupted live site and restore again from the development area, which could be a good course of action?

Thank you for your time.


Akeeba Staff

First things first. We need to know what causes the blank page.

A white page or a page with a 500 Internal Server Error is, in fact, either a .htaccess issue to a PHP fatal error in disguise.

First, let's see if it is a .htaccess issue. Try renaming the .htaccess file in your site's root to htaccess.bak If there is a .htaccess file in the site's administrator directory, try renaming it as well. If that solves the problem, the issue was with a directive in your .htaccess file. We'd like to recommend you to try removing directives from your .htaccess until you find the one which causes the problem.

If that doesn't help, the error you are receiving is in fact a PHP error in disguise. First, check your server's error logs (not the access logs) immediately after visiting the page which throws the error. There should be an exact description of the PHP fatal error which occurred. Sometimes you can find the error messages in files called error_log or error.log inside the site's root and/or administrator directories. If unsure about the error log location, please consult your host. Most likely the error logs are available in your site's cPanel, Plesk control panel or similar hosting account management facility.

If your host does not give you access to the error logs and you have access to the Joomla! administrator area, please log in to your site's back-end, go to Global Configuration, click on the Server tab and set the Error Reporting to Maximum (Joomla! 1.5) or Development (Joomla! 2.x and later). Try visiting the problem page again.

If you still get a blank page, edit your configuration.php file and put the following code right after the final closing curly brace ( this is what a curly brace looks like --> } ) but before the closing PHP tag (it looks like ?> that is a question mark and a greater-than sign):

ini_set( 'display_errors', true );
error_reporting( E_ALL ); 

Try visiting the problem page again.

If you still get a white page, please remote the two lines from your configuration.php file. Edit the .htaccess file in your site's root. If you don't have a file named .htaccess create a new one. Beware that htaccess.txt is a DIFFERENT FILE and will NOT work! Add the following to the end of the file:

php_flag display_errors On
php_value error_reporting 32767

and retry loading the problem page.

If you still get a white page, remove the two lines from your .htaccess file. Now, create a file called php.ini with the following content:


and upload it into your site's root and your site's administrator directory. Retry loading the problem page.

If you still get a white page, delete the php.ini files your created and choose a different host. If your host doesn't allow you to debug any PHP-related issues there is no point paying them.

Please note that if you can not understand what the PHP error message means, just copy and paste it here verbatim so that we can take a look and point you to the right direction.

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: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

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!

Summer vacations: Our support will be closed for replies and new tickets from August 6th to August 21st, 2022 due to summer vacations.