Support

Admin Tools

#24045 Creation of a file “restoration.php” after the update in 3.4.8

Posted in ‘Admin Tools 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
Admin Tools version
n/a

Latest post by nicholas on Monday, 28 December 2015 01:44 CST

Monday, 28 December 2015 00:36 CST

[email protected]
 Hello
After the update of a website from Joomla 3.4.7 to 3.4.8, it has been created the file “restoration.php” (administrator/components/com_joomlaupdate/restoration.php) with the following content:
<?php
defined('_AKEEBA_RESTORATION') or die('Restricted access');
$restoration_setup = array(
'kickstart.security.password' => 'χχχχχχχχχχχ .....χχχχ',
'kickstart.tuning.max_exec_time' => '5',
'kickstart.tuning.run_time_bias' => '75',
'kickstart.tuning.min_exec_time' => '0',
'kickstart.procengine' => 'direct',
'kickstart.setup.sourcefile' => 'C:\xampp\htdocs\mysite/tmp/Joomla_3.4.7_to_3.4.8-Stable-Patch_Package.zip',
'kickstart.setup.destdir' => 'C:\xampp\htdocs\mysite',
'kickstart.setup.restoreperms' => '0',
'kickstart.setup.filetype' => 'zip',
'kickstart.setup.dryrun' => '0');

In other websites it has not been created the previous file.
Is it normal or it is something dangerous? Must be removed or be renamed the file restoration.php? Should i reset the file restore.php from an older backup?

Also I inform you that the administrator area is protected and hided. I read your previous answer (https://www.akeebabackup.com/home/news/1605-security-update-sep-2014.html) but I would need some more help.

Please inform me about what should i do?
Thank you

Monday, 28 December 2015 01:44 CST

nicholas
Please note that we do NOT provide generic Joomla! support. Use the Joomla! forums for that.

I'll just say this and close this ticket: this file is normal and should have been removed after the update. However, I believe that for this to happen you'd have to log back in and go back to com_joomlaupdate. You can safely remove that file. It is only used during the upgrade to let Joomla!'s copy of restore.php (this is the brains of Kickstart which we kindly donated to Joomla! back in Joomla! 2.5.1) extract the update ZIP file.

Why is this file left behind? Joomla! 3.4.7 was broken because the fix applied for the PHP session bug had a major bug of its own which caused myriad problems. The only way to work around that Joomla! 3.4.7 bug was to kill all sessions upon upgrading to Joomla! 3.4.8. Unfortunately, this means that com_joomlaupdate cannot perform its final cleaning task of removing the temporary restoration.php file and the update ZIP file from the temporary directory. It was either that or leaving you guys and gals with broken sites to which you could not log in :(

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!