Support

Site Restoration

#30390 ANGIE Exception - String could not be parsed as XML

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 sebtombs on Monday, 22 October 2018 09:17 CDT

sebtombs
Hi. When restoring from an Akeeba Solo backup, after restoration of the database has finished, I am getting:

Exception — String could not be parsed as XML

#0 /home/newsite/public_html/installation/platform/models/magentoconfiguration.php(66): SimpleXMLElement->__construct('/home/newsite/p...', 0, true)
#1 /home/newsite/public_html/installation/platform/models/magentoconfiguration.php(24): AngieModelMagentoConfiguration->loadFromFile('/home/newsite/p...')
#2 /home/newsite/public_html/installation/framework/model/model.php(158): AngieModelMagentoConfiguration->__construct(Array, Object(AContainer))
#3 /home/newsite/public_html/installation/angie/models/base/setup.php(30): AModel::getAnInstance('Configuration', 'AngieModel', Array, Object(AContainer))
#4 /home/newsite/public_html/installation/framework/model/model.php(158): AngieModelBaseSetup->__construct(Array, Object(AContainer))
#5 /home/newsite/public_html/installation/framework/controller/controller.php(630): AModel::getAnInstance('Setup', 'AngieModel', Array, Object(AContainer))
#6 /home/newsite/public_html/installation/framework/controller/controller.php(921): AController->createModel('Setup', 'AngieModel', Array)
#7 /home/newsite/public_html/installation/framework/controller/controller.php(579): AController->getModel('Setup', 'AngieModel', Array)
#8 /home/newsite/public_html/installation/framework/controller/controller.php(539): AController->getThisModel()
#9 /home/newsite/public_html/installation/framework/controller/controller.php(554): AController->display()
#10 /home/newsite/public_html/installation/framework/controller/controller.php(511): AController->main()
#11 /home/newsite/public_html/installation/framework/dispatcher/dispatcher.php(267): AController->execute('default')turned o
#12 /home/newsite/public_html/installation/framework/application/application.php(182): ADispatcher->dispatch()
#13 /home/newsite/public_html/installation/index.php(76): AApplication->dispatch()
#14 {main}


I have looked at ticket 14060, which suggests that the problem could be due to PHP not having XML support enabled. However, I seem to have libxml present.

The backup was taken from a proprietary shared hosting solution but is being restored to a Virtualmin server.

This may be irrelevant, but the site does not actually use Magento.

nicholas
Akeeba Staff
Manager
The problem is that you have used the wrong site type when taking the backup. By choosing the Magento site type the restoration script added to the backup is the Magento one. This restoration script is trying to load a configuration file that's specific to Magento and comes in XML format. Since that file does not exist you get an error.

The correct solution is to set up the backup with the site type and ANGIE installer "Bespoke PHP script", take a new backup and restore that new backup. The bespoke PHP site restoration script does not try to load any configuration file, therefore it will work for you.

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!

sebtombs
Many apologies, you are quite right - the site type was correct but I'd somehow set the ANGIE Installer to Magento (probably a scroll wheel mistake when changing backup location to a different S3 bucket).

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!