If you’ve noticed that your system.log’s size is increasing every minute because of the error logs like this:
Warning: simplexml_load_string(): ^ in /lib/Varien/Simplexml/Config.php on line 383
2016-06-27T14:01:04+00:00 ERR (3): Warning: simplexml_load_string(): Entity: line 292: parser error : expected '>' in /lib/Varien/Simplexml/Config.php on line 383
2016-06-27T14:01:04+00:00 ERR (3): Warning: simplexml_load_string(): nkey.png</233><234>manufacturers/image.jpg</234><235>manufacturers/image.jpg</ in /lib/Varien/Simplexml/Config.php on line 383
2016-06-27T14:01:04+00:00 ERR (3): Warning: simplexml_load_string(): ^ in /lib/Varien/Simplexml/Config.php on line 383
2016-06-27T14:01:04+00:00 ERR (3): Warning: simplexml_load_string(): Entity: line 292: parser error : Opening and ending tag mismatch: config line 1 and unparseable in /lib/Varien/Simplexml/Config.php on line 383
2016-06-27T14:01:04+00:00 ERR (3): Warning: simplexml_load_string(): nkey.png</233><234>manufacturers/image.jpg</234><235>manufacturers/image.jpg</ in /lib/Varien/Simplexml/Config.php on line 383
Then consider your problem solved. After hours and hours of googling and searching at stackoverflow, I found nothing. Most of the solutions to the problem that is related to the simplexml_load_string error is something that is related to an XML file. But my problem wasn’t.
To be honest, what actually helped me is this post in German. Because it gave me a hint of where to look at. I thought the problem is within my Magento files, so I disabled all third party modules, but the system log still logs the simplexml_load_string() warning over and over again.
So because of the post from neoshops.de, I then checked my core_config_data, and deleted all tables rows that was inserted by the Ma2_Manufacturers_Free module, and it did the trick. My problem was solved! No more error logs that reaches 1GB or more. Everything is now running smoothly in our Magento site.
Leave a Reply