Understanding Browser Caching
When you visit a website for the first time, your browser communicates with the server hosting the site. The browser sends a request, and the server responds with the website's assets. This process uses bandwidth, and some web pages may take a long time to fully load due to their numerous or large assets. Browser caching improves and speeds up browsing. Once you've downloaded an asset, it temporarily resides on your machine. When you revisit the same page, the load time is faster since your browser can pre-populate those downloaded assets.
Impact on Your Organization
Sometimes, changes in your CRM or backend, such as portal design updates, may take time to appear on the Portal, especially for pages you've previously visited. This delay can lead users to think their changes didn't take effect, causing confusion and issues when making multiple updates. To avoid this, it's recommended to always clear your browser cache after making any major change that appears on the Portal.
If you have bookmarked a session in the CRM or Portal, you may need to update the bookmark if it is for a specific process (such as a Class Registration/Meeting Registration - these use specific IDs to denote the unique session and bookmarking them can cause caching issues). Press CTRL+D on your keyboard, click on Remove, and then press CTRL+D again to re-bookmark the session.
How to Clear the Browser Cache
- Log completely out of your CRM and start with a fresh browser instance. This should resolve most caching issues.
- If you're still seeing errors, press CTRL+SHIFT+R to perform a hard reload of the page. This is useful if you are changing one thing on one page multiple times.
- If the error persists, press CTRL+SHIFT+DEL on your keyboard to open your browser’s Clear Data window. Select the option to clear the Cache and confirm. This will ensure your browser’s cache is completely cleared.
Examples of the Clear Data window
Google Chrome
Mozilla Firefox
Microsoft Edge
What to do if the above doesn't work?
If the above methods do not work to display the changes on the Portal, it may be possible that things are cached on the back-end. In this case, please submit a Support ticket and we will be happy to clear things out on our side for you.