Magento CMS error: the front controller reached 100 iterations on the router side

When I create a page through CMS (in the administrator), everything seems fine, but when I try to access the page in the interface, I get a blank page with an error:

Front controller reached 100 router match iterations #0 ..\app\code\core\Mage\Core\Controller\Varien\Front.php(183): Mage::throwException('Front controlle...') #1 ..\app\code\core\Mage\Core\Model\App.php(340): Mage_Core_Controller_Varien_Front->dispatch() #2 ..\app\Mage.php(627): Mage_Core_Model_App->run(Array) #3 ..\index.php(80): Mage::run('', 'store') #4 {main} 

Any idea?

Thanks!

+4
source share
2 answers

We had this mistake in the past. This is because Magento does not load the Cms module. No router on the system matches the URL, so the default router sets the path as the 404 page set in the admin panel. The default value for this is the Cms index controller, so if the Cms module is not loaded, it ends in an infinite loop.

The reason is a little harder to guess. In our case, we found that the cache was damaged when the system was under heavy load, and we cleared the cache directory. It can be fixed by running rm -rf var/cache/mage--* until the page rm -rf var/cache/mage--* successfully. Another reason is to disable the cms module in app/etc/modules .

+3
source

This is a really good record of what is happening to create the condition you describe. https://github.com/convenient/magento-ce-ee-config-corruption-bug

The bottom line is that there is an error that allows two processes to cancel and at the same time try to restore the cache. This issue has been addressed on the official Magento SUPEE-4755 plugin.

This can also be found on the magento stack website.

+1
source

Source: https://habr.com/ru/post/1391883/


All Articles