Mila Posted December 5, 2017 Share Posted December 5, 2017 Hi, I did migration of website and since then I do have this error message in my BackOffice every time I login: Error found : StartTag: invalid element name in must_have_module_list.xml file. I did clean cache, checked permissions of this file and carpet where it´s allocated, deleted the must_have_module_list.xml file in public html/config/xml and the message didn´t disappear. Also I tried replace this file by old one which I had before migration and it didn´t work as the system generates new one with error. Can anybody help with this? Thank you. Link to comment Share on other sites More sharing options...
bellini13 Posted December 7, 2017 Share Posted December 7, 2017 I would suggest reporting the issue to Prestashop via their forge system. if you open the xml file in question, you will see that the file contents contain html content with a 301 redirect. This means Prestashop backend server is not working properly. Link to comment Share on other sites More sharing options...
ILja Posted February 7, 2018 Share Posted February 7, 2018 (edited) I had same error. Problem was from pm_advancedtopmenu module. There is in pm_advancedtopmenu.php function, that changing xml file. private function _MHM_update() { if ($this->_MHM_needUpdate()) { $this->initClassVar(); $content = file_get_contents(_PS_ROOT_DIR_.Module::CACHE_FILE_MUST_HAVE_MODULES_LIST); if (strlen($content) == 0) $content = '<?xml version="1.0" encoding="UTF-8"?><modules></modules>'; $new_content = Tools::file_get_contents('http://www.presta-module.com/cross-selling-addons-modules-footer?xml=1&iso='.$this->_iso_lang.'&pm='.$this->_getPMdata()); if ($new_content !== false) { $content = str_replace('<modules>', '<modules><!-- PM_MODS -->'.$new_content.'<!-- /PM_MODS -->', $content); @file_put_contents(_PS_ROOT_DIR_.Module::CACHE_FILE_MUST_HAVE_MODULES_LIST, $content); } else { $content = str_replace('<modules>', '<modules><!-- PM_MODS --><!-- /PM_MODS -->', $content); @file_put_contents(_PS_ROOT_DIR_.Module::CACHE_FILE_MUST_HAVE_MODULES_LIST, $content); } } } For fix it, we need to change link from "http://..." to "https://..." Edited February 7, 2018 by ILja (see edit history) Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now