Why WISECP Product Changes Do Not Appear Instantly: A Datawise Page Cache Guide

Why WISECP Product Changes Do Not Appear Instantly: A Datawise Page Cache Guide

A common issue on WISECP websites is this: you update a product or service in the admin panel, but the change does not appear immediately on the front end. The page continues to show the old version. Then you open the related FonPageBuilder page, click edit and save without changing anything, and suddenly the latest content appears. It feels strange at first, but the explanation is usually very simple: page caching.

The Datawise documentation clearly states that the Page Cache option stores the content of pages created with FonPageBuilder so they can load faster. The same documentation also recommends keeping this option disabled during development and setup. In other words, the system already gives the trade-off away: caching improves speed, but during active editing it can delay what you see on the front end.

That is exactly what happened in this support case. After a recent update, the customer noticed that product and service changes made inside WISECP were not immediately reflected on the site. However, if they opened the related product group page in FonPageBuilder and simply clicked save, the new version appeared right away. In testing, disabling the cache pages created with FonPageBuilder option in Datawise settings made the issue disappear, and changes started showing instantly again.

The main lesson here is that the Datawise page cache stores HTML output for FonPageBuilder pages for performance reasons. Datawise update notes explain that this cache system was improved so that the page loads normally on the first visit, is served from cache on later visits, and is automatically refreshed when the page itself is changed or when exchange rates are updated. The same notes also state that cache can be cleared manually from the theme settings.

The support case reveals the more practical detail: when a FonPageBuilder page is edited, cache refresh is triggered as expected, but some product or category changes may not always trigger the same invalidation flow. So if a Builder page is displaying product boxes, package lists, or category content, the visible page may continue serving older cached HTML even though the product record itself has already been updated. In other words, the issue is often not “the product was not saved,” but “the page output was not regenerated yet.”

The most practical workflow is straightforward.

If you are still building the site or making frequent edits, keep the Page Cache option disabled in Datawise settings. The documentation explicitly recommends this during development and setup. Once the site is stable, you can enable it again for performance.

If the live site needs caching enabled and product or package changes are not showing immediately, clearing cache from the theme settings after product updates is a reasonable step. Datawise update notes confirm that manual cache clearing is supported from the theme settings.

Another important point is that clearing browser history alone is not always enough. Datawise update notes describe how optimization and caching layers such as Cloudflare and Rocket Loader can affect JavaScript execution order and change front-end behavior. That means the issue may not be the browser at all, but server-side caching, CDN behavior, or another optimization layer.

What makes this support case useful is how quickly the problem was isolated. As soon as the customer disabled page caching in the setting shown in the screenshot, the changes started appearing immediately. Tests like this are valuable because they prevent unnecessary file edits and random guesswork, which humans seem to enjoy far more than they should.

In short, delayed product updates on WISECP are often not caused by a broken product setup but by how Datawise page caching works. For pages built with FonPageBuilder, caching improves performance, but it should be used carefully on sites where products change frequently. The safest approach is simple: disable cache during editing, enable it later for performance, and manually clear cache after product changes when needed. The more permanent long-term fix is to improve automatic cache invalidation for product and category updates as well.

• Wisecp Themes >>
• Wisecp Datawise Theme >>
• Wisecp Prusa Theme >>