How to Clear the Magento 1.6 Cache
In this tutorial:
Magento 1.6 by default includes a caching system to help improve the performance. When you make changes to your Magento website, you may not see the changes immediately. In cases where you want to see the changes you have made to your “live” Magento 1.6 website, you’ll need to clear the cache files. Clearing the Magento 1.6 cache files is easily accomplished in the Magento Admin Backend.
Please feel free to visit our other Magento Tutorials in our Education Channel.
Clearing Cache in the Admin Panel
- Log into your Magento Admin Panel
- Go to System ->> Cache Management
- Click on the “Flush Cache Storage” button
Let’s take a quick look at the difference between the “Flush Magento Cache” and “Flush Cache Storage” functions. “Flush Cache Storage” removes all the cache files regardless of any perimeters. “Flush Magento Cache” tries to do a check for invalidated pages and will remove them accordingly. If you’re unsure of which to use, using the “Flush Cache Storage” will ensure that ALL CACHE FILES are removed.
Manually Clearing the Magento Cache
You can clear the Magento 1.6 cache manually as well. If you’re working in FTP or cPanel File Manager and need to quickly clear your Magento 1.6 Cache files it’s relatively easy. All the cache files for Magento are stored in the /var/cache folder.
- With your FTP program or cPanel File Manager, navigate to the root directory of your Magento cart
- Open the var/cache folder
- Select all the contents in the folder and delete them
Now, when you refresh your website, you should be able to see all the changes you have made.
If you need further assistance please feel free to ask a question on our support center.
2015-04-09 11:16 am
My sessions are set <session_save><![CDATA[db]]></session_save>, so I have no files to flush. What about flushing core_sessions table?
Thanks James Niland
2015-04-09 4:36 pm
Thank you for your question. The core_sessions table typically stores information such as the customer's cart contents, and not the cache of your site.
I found a post online where they offer alternate suggestion, but you will have to test it to verify whether it works for you. (I recommend backing up your site first).