Support

Site Restoration

#15001 Restore won't proceed past initial screen, JS error

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
n/a
CMS Type
Other
CMS Version
n/a
Backup Tool Version
n/a
Kickstart version
n/a

Latest post by nicholas on Tuesday, 12 February 2013 08:10 CST

Tuesday, 12 February 2013 07:59 CST

sackerman

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.9
PHP version: 5.3.21
MySQL version: 5.5.30
Host: (optional, but it helps us help you)
Akeeba Backup version which took the backup: 3.6.12
Kickstart version used to extract the backup: Using Zip

Description of my issue: I have restored the site, all of the initial screen checks are green, all permissions on files have been checked but when I click the 'Next' button nothing happens. I have tried this in both 'Chrome' and 'Firefox' and get same results. I have deleted all files made another backup, restored and get get same results. Firebug is throwing the following error when I click 'Next':

SyntaxError: identifier starts immediately after numeric literal
javascript:submitForm('dbnext')?CSRF_TOKEN=5e960059c195f89e2ddaadbece2e3d29ef8a9538
Line 1

Have done this many,many times and never had a problem. However I have just upgraded to 3.6.12 and this is the first restore done with that version.

Tuesday, 12 February 2013 08:10 CST

nicholas

This extra stuff which causes the Javascript error (?CSRF_TOKEN=5e960059c195f89e2ddaadbece2e3d29ef8a9538) does not come from any code I have ever written in the last 6 years. This leaves us with one of the following possibilities:

  • You have a browser plugin which actively screws up Javascript on the page. Please try using a different browser.
  • You have an Internet security / antivirus application which screws up Javascript on the page. Please try using a different computer or turn off your Internet security / antivirus application (and reboot).
  • Your ISP or company proxy server is actively screwing up Javascript on the page. Use a different Internet connection.
  • You have something in your .htaccess which causes this issue. Normally, when restoring, the .htaccess file is renamed to htaccess.bak. In case that file is unwriteable it can't be renamed. Try removing it manually before clicking the "Run the Installer" button.
  • Something on your server is causing this. I can't help you with that. Maybe your host can.

For what is worth, please let me clarify the following:

  • The installation script has not received an update since Akeeba Backup 3.6.11. The upgrade to 3.6.12 is completely irrelevant to this issue.
  • That CSRF_TOKEN variable is NOT added by any code I have ever written since I first released JoomlaPack 1.0 Beta in November 2006. It's added by third party code of dubious quality which pre-processes the HTML output before sending it to the browser.
  • As a result, I cannot provide much help for resolving an issue which is not caused by my software. At best I can provide you some generic advice. Maybe you should try restoring the same backup on a different host (a free demo account at CloudAccess.net works wonders) using a different computer, browser and Internet connection. Since that will work you will understand the validity of my points above.

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!