MetaLocator caches your Interface output for optimal performance. This can mean that changes to your interface can be delayed for up to 15 minutes before they will appear on an Interface deployed to your Web site.
However, the interface as viewed through the "Preview" link is not cached and reflects your latest settings immediately. This allows you to make changes to your interface and view those results immediately.
When testing or making changes to your Interface or data, you should always use the provided preview link, as shown below to ensure you are seeing your latest changes:
There are two types of caching used within MetaLocator, a server-side cache and a browser-based cache. Both caches only apply to the Interface when it is deployed to your Web page. Therefore, previewing changes on your website, versus the "Preview" link above, can be difficult if you don't understand how the MetaLocator caches can be cleared.
To clear the server-based cache, you can simply save your Interface. Any time the Interface is saved, the server-side cache is cleared. The server side cache is also cleared every 15 minutes automatically.
There is also a browser-based cache, which resides in your browser, and is specific to your computer. To clear this cache, follow these instructions on clearing your browser cache
If you encounter a scenario where you want to force your website visitor's cache of the Interface to be forcibly ignored, you can change the code that was deployed to your page. Again, this is rarely necessary.
The code you deployed on your page looks like this:
Changing it to this, forces a browser to treat it as a new resource
Notice the added &cachebust=12345. This parameter is totally arbitrary, and serves only to change the URL. I could have added &this=that, or &favoritesoftware=metalocator.
This will change the URL and cause the script to be refreshed in the user's browser.