{"id":9507,"date":"2026-06-03T05:49:57","date_gmt":"2026-06-03T03:49:57","guid":{"rendered":"https:\/\/mybox.com\/help\/?post_type=manual_kb&#038;p=9507"},"modified":"2026-06-08T09:47:16","modified_gmt":"2026-06-08T07:47:16","slug":"erori-xml-in-prestashop-cum-sa-le-depistezi-si-sa-le-remediezi","status":"publish","type":"manual_kb","link":"https:\/\/mybox.com\/help\/ro\/knowledgebase\/xml-errors-in-prestashop-how-to-diagnose-and-fix-them\/","title":{"rendered":"Erori XML \u00een PrestaShop: Cum s\u0103 le diagnostica\u021bi \u0219i s\u0103 le remedia\u021bi"},"content":{"rendered":"<div class=\"translation-block translation-block-merged\">\n<p class=\"wp-block-paragraph\">PrestaShop may sometimes display errors related to XML files in the administration panel. These errors usually appear when PrestaShop cannot correctly read a file downloaded from the PrestaShop Addons service.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Common examples include:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Error found: Extra content at the end of the document in country_module_list.xml file<br>Error found: Sequence ']]>' not allowed in content in country_module_list.xml file<br>Error found: Premature end of data in tag badge line 1 in must_have_module_list.xml file<br>Error found: StartTag: invalid element name in country_module_list.xml file<\/code><\/pre>\n\n\n\n<\/div>\n\n<div id=\"mybox-1781287387\" class=\"mybox-content mybox-entity-placement\"><div class=\"early-access-banner-inpost\">\r\n  <div class=\"banner-left-inpost\">\r\n    <div class=\"icon-box-inpost\">\r\n      <img decoding=\"async\" src=\"https:\/\/mybox.com\/help\/wp-content\/uploads\/2026\/02\/square-info-icon.svg\" alt=\"Info\">\r\n    <\/div>\r\n    <div class=\"text-box-inpost\">\r\n      <span class=\"label-inpost\"><span class=\"translation-block translation-block-banner-text\">Acces timpuriu<\/span><\/span>\r\n      <h4><span class=\"translation-block translation-block-banner-text\">Mai ave\u021bi nevoie de ajutor?<\/span><\/h4>\r\n      <p><span class=\"translation-block translation-block-banner-text\">Contacta\u021bi echipa noastr\u0103 de servicii pentru clien\u021bi.<\/span><\/p>\r\n    <\/div>\r\n  <\/div>\r\n\r\n  <div class=\"banner-right-inpost\">\r\n    <a href=\"https:\/\/panel.mybox.com\/helpdesk2\/v\/list\/\" class=\"banner-button-inpost\"><span class=\"translation-block translation-block-banner-text\">Trimite mesaj<\/span><\/a>\r\n  <\/div>\r\n<\/div><\/div>\n\n<div class=\"translation-block translation-block-merged\"><p class=\"wp-block-paragraph\">These messages usually indicate that one of the XML files used by PrestaShop is incomplete or corrupted.<\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_86 ez-toc-wrap-left counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/xml-errors-in-prestashop-how-to-diagnose-and-fix-them\/#Why_This_Happens\" >Why This Happens<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/xml-errors-in-prestashop-how-to-diagnose-and-fix-them\/#Solution_Delete_the_Corrupted_XML_File\" >Solution: Delete the Corrupted XML File<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/xml-errors-in-prestashop-how-to-diagnose-and-fix-them\/#Clear_the_PrestaShop_Cache\" >Clear the PrestaShop Cache<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/xml-errors-in-prestashop-how-to-diagnose-and-fix-them\/#Alternative_Solution\" >Alternative Solution<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/xml-errors-in-prestashop-how-to-diagnose-and-fix-them\/#Important_Note\" >Important Note<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/xml-errors-in-prestashop-how-to-diagnose-and-fix-them\/#Summary\" >Summary<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Why_This_Happens\"><\/span>Why This Happens<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">PrestaShop regularly connects to the Addons module directory to download module-related XML files.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the connection is interrupted, or if the external server does not respond correctly, the XML file may be saved only partially. When PrestaShop later tries to read that file, it detects invalid XML structure and displays an error in the back office.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This issue is usually related to cached or incomplete XML data, not to the products or orders in your store.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Solution_Delete_the_Corrupted_XML_File\"><\/span>Solution: Delete the Corrupted XML File<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before making changes, create a backup of the affected file.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Connect to your store files using FTP.<\/li>\n\n\n\n<li>Go to the following directory:<\/li>\n<\/ol>\n\n\n\n<pre class=\"wp-block-code\"><code>\/config\/xml<\/code><\/pre>\n\n\n\n<ol start=\"3\" class=\"wp-block-list\">\n<li>Locate the XML file mentioned in the error message.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>default_country_modules_list.xml<\/code><\/pre>\n\n\n\n<ol start=\"4\" class=\"wp-block-list\">\n<li>Download a copy of the file to your computer as a backup.<\/li>\n\n\n\n<li>Delete the file from the server.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">PrestaShop should download the file again later, usually in the correct format.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Clear_the_PrestaShop_Cache\"><\/span>Clear the PrestaShop Cache<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">After deleting the corrupted XML file, clear the store cache.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">From the PrestaShop back office, go to:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Advanced Parameters \u2192 Performance \u2192 Clear cache<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can also clear the cache manually through FTP by going to:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\/cache\/smarty\/compile<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Delete the directories located inside this folder.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not delete the <code>compile<\/code> folder itself.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Alternative_Solution\"><\/span>Alternative Solution<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If deleting the XML file and clearing the cache does not resolve the issue, the connection to the PrestaShop Addons service can be disabled in the PrestaShop files.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This requires editing a core file, so create a backup before making changes.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Connect using FTP.<\/li>\n\n\n\n<li>Open the following file:<\/li>\n<\/ol>\n\n\n\n<pre class=\"wp-block-code\"><code>\/classes\/Tools.php<\/code><\/pre>\n\n\n\n<ol start=\"3\" class=\"wp-block-list\">\n<li>Find this line:<\/li>\n<\/ol>\n\n\n\n<pre class=\"wp-block-code\"><code>protected static $is_addons_up = true;<\/code><\/pre>\n\n\n\n<ol start=\"4\" class=\"wp-block-list\">\n<li>Replace it with:<\/li>\n<\/ol>\n\n\n\n<pre class=\"wp-block-code\"><code>protected static $is_addons_up = false;<\/code><\/pre>\n\n\n\n<ol start=\"5\" class=\"wp-block-list\">\n<li>Save the file and clear the PrestaShop cache again.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Important_Note\"><\/span>Important Note<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Editing core PrestaShop files should be treated as a temporary workaround. Core changes may be overwritten during future PrestaShop updates.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the issue returns frequently, check whether your store can reliably connect to the PrestaShop Addons service and whether any firewall or server security rules are interrupting outgoing connections.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Summary\"><\/span>Summary<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">XML errors in PrestaShop usually happen when module-related XML files are downloaded incompletely or become corrupted. In most cases, deleting the affected XML file from <code>\/config\/xml<\/code> and clearing the cache resolves the issue. If the problem persists, disabling Addons requests in <code>Tools.php<\/code> may be used as a temporary workaround.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n<\/div>","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"template":"","format":"standard","manualknowledgebasecat":[125],"manual_kb_tag":[447,5299,5300,5301,5302,5303,5304,5305,5306,5307],"class_list":["post-9507","manual_kb","type-manual_kb","status-publish","format-standard","hentry","manualknowledgebasecat-websites","manual_kb_tag-prestashop-addons","manual_kb_tag-prestashop-errors","manual_kb_tag-xml-parsing-errors","manual_kb_tag-corrupted-xml-files","manual_kb_tag-incomplete-file-download","manual_kb_tag-partial-file-download","manual_kb_tag-module-xml-files","manual_kb_tag-default-country-modules-list","manual_kb_tag-config-xml-directory","manual_kb_tag-delete-corrupted-file"],"_links":{"self":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/9507","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb"}],"about":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/types\/manual_kb"}],"author":[{"embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":2,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/9507\/revisions"}],"predecessor-version":[{"id":9508,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/9507\/revisions\/9508"}],"wp:attachment":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/media?parent=9507"}],"wp:term":[{"taxonomy":"manualknowledgebasecat","embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manualknowledgebasecat?post=9507"},{"taxonomy":"manual_kb_tag","embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb_tag?post=9507"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}