Support

Akeeba Backup for Joomla!

#13215 Restoring site to a subfolderon hosting server.

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 on Wednesday, 12 September 2012 18:00 CDT

user67223
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: (2.5.6)
PHP version: (5.5)
MySQL version: (5.0)
Host: (GoDaddy.com)
Akeeba Backup version: (3.6.1)

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:
After complating the restoration I get the following error.
Parse error: syntax error, unexpected $end in /home/content/74/9321674/html/test/components/com_content/models/articles.php on line 238

I am backing up www.redstonewarrants.com and restoring to www.redstonewarrants.info. '.info' is pointed to the /test folder in my root of the host.

nicholas
Akeeba Staff
Manager
There is no such thing as PHP version "5.5" yet. Please check your PHP version on the restored site. You are using a version older than 5.3, that's why you get the errors which are not in any way related to Akeeba Backup.

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!

user67223
Nicholas,
You are partly correct. I misheard the GoDaddy Support Rep when he gave me the PHP version. However, it is PHP 5.3 according to the Hosting manager. Please see the attached screen shot.

nicholas
Akeeba Staff
Manager
OK, that's more like it :) There is another possibility: did you try restoring your site on top of an existing Joomla! 1.5, 1.6, 1.7 or 2.5 site?

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!

user67223
Nope. I restored to an empty folder.

nicholas
Akeeba Staff
Manager
Take a look at the referenced file (components/com_content/models/articles.php) on your restored and your original site. Do their sizes match? If not, did you receive any errors while restoring your site?

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!

user67223
There were no errors duriing backup or during restoration.

When I checked the current file on the site, it had the same size as the backed up file. However, we had made a number of changes to the site since I did the backup. I figured that there may have been resultant changes to that file and size agreement now was no longer pertinent.

I also figured my best bet at this point was to do a complete new backup and restore. So I did, and it worked flawlessly.

I have no idea what was wrong with the first trial, but I don't really need to know. Maybe I wasn't wearing my yellow socks that day. :)

If anyone reports that same error, suggest that they make a new backup and restore it.

In any case you may close this ticket. Thank you for attempting to unravel the mistery.

nicholas
Akeeba Staff
Manager
Actually, I do have an idea what went on. For some reason, PHP 4 was being used by default in the first try. I just realised you are on GoDaddy. If I recall correctly, you need to use some special .htaccess directives to make PHP 5.3 the PHP version to be used on your site, otherwise it's using PHP 4. GoDaddy, unlike all other hosts, takes 10-30 minutes to apply .htaccess file changes. During the restoration the .htaccess file is removed and rewritten. The problem was either the time gap between rewritting and reapplying the .htaccess file, or that the .htaccess file wasn't restored correctly on the first try.

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!

System Task
system
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.

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!