To make changes to the kernel configuration and force them to stick (local.xml, base URLs, etc.), you need to clear the Magento cache code, often manually deleting the mage--?
subfolders mage--?
in var/cache/
.
Caching configurations can cause all kinds of headaches, including base URLs that still indicate the initial installation of Magento (different folders, different servers), even though you can use phpMyAdmin and see that the rows have been updated in the database, The configuration will not be re-read from the database until the cached configuration information is deleted.
The other place where the material is stuck is in the op-code APC cache if you use it. Use the apc.php
administration apc.php
to clear it. Stopping and restarting Apache will achieve the same result
And finally, if YOU DO NOT HAVE PERMISSIONS FOR var/cache/
AND var/tmp/
SO THEY ARE SECURED AND PROHIBITED BY YOUR WEB SERVER, Magento can store cached information in the /tmp
system , which means that no clearing of the Magentos cache is possible will cause the cached configs to disappear until someone reboots the server, the /tmp
system will be cleared, and Magento will apparently read its configs automatically. Or they tell you this, and you have access to delete the Magento cache from /tmp
. Here is some documentation that this happens in the temporary storage folder of the system with the root (see. Images)
Note. . If you back up your local.xml
file, rename it to something like local.xml.sv1
or you will find that Magento is still reading it.
source share