Wix Studio Dynamic Content Sometimes Shows Older Data After the Website Page Loads

Ask the community
, , ,
1

Hi All,

I am experiencing a strange issue with a Wix Studio website where a dynamic content section sometimes displays older information even though the underlying content has already been updated. The website uses a dynamic dataset to display information on a page, and normally the latest values appear correctly when visitors open the page. However, on some visits the page loads successfully but the dynamic section shows a previous version of the content instead of the latest version that is currently stored in the CMS. The rest of the page appears to load normally, so this is not a situation where the entire website is unavailable or the page completely fails to render. The specific problem is that the dynamic content appears to be using an older version of the data after the page has loaded. If I later refresh the browser, the updated information can appear correctly, which makes me suspect that the page is not always retrieving the newest dataset values during its initial load. I am trying to understand whether this could be related to the way Wix Studio handles dynamic datasets, page initialization, caching, or client-side data retrieval.

The behavior is intermittent, which makes it particularly difficult to reproduce consistently. I can make an update to an item in the Wix CMS and confirm that the new value is present in the collection, but when I open the corresponding website page, there are occasions where the older value is still displayed. If I refresh the page again, the new value may then appear without any further change to the CMS item. This makes the situation confusing because the content itself appears to be correct in the CMS, and the website eventually displays that same updated content, but the first page load does not always use it. I have also noticed that the issue seems more noticeable when navigating between pages within the website rather than opening the dynamic page directly in a completely new browser session. Because Wix Studio pages can use client-side navigation and dynamic datasets, I am wondering whether the dataset is sometimes retaining previously loaded information instead of requesting the current record again when the visitor arrives at the page. I would like to know if there is a recommended way to force a dynamic dataset to refresh when a page becomes active without creating unnecessary requests or affecting the normal loading behavior.

I have already checked the CMS collection itself and confirmed that the updated records are being saved correctly. The problem therefore does not appear to be caused by the content update failing to save. I have also reviewed the dataset connection for the affected elements and verified that the displayed fields are connected to the intended collection fields. The dynamic page structure itself is also functioning because it can display the correct information after a refresh. What I am trying to identify is why the same page can sometimes display an older value during one visit and the current value during another visit when the CMS contains only the current version. I have considered whether browser caching might be involved, but the behavior does not seem limited to one particular browser session, and simply waiting for the page to finish loading does not always result in the newest value appearing. I would therefore like to understand whether Wix Studio has any caching or dataset lifecycle behavior that could cause a previously retrieved collection item to remain available to the page after the underlying CMS content has changed.

Another detail that makes me think this may be related to the dynamic dataset lifecycle is that the page itself does not look broken when the stale information appears. The layout, text elements, images, and other static portions of the page load normally, while the specific dynamic values are the ones that can occasionally be outdated. There are no obvious visual indicators telling me that the dataset has failed, so a visitor could easily assume that the older information is still current. I have looked at the page logic and am trying to avoid adding unnecessary refresh operations everywhere because I want to understand the intended Wix Studio behavior first. If there is a recommended event or dataset method that should be used when a dynamic page is loaded or revisited, I would like to know whether that method can ensure that the current collection record is retrieved. I am particularly interested in whether dataset readiness events, page navigation events, or explicit refresh methods are appropriate for this situation, and whether using one of them could reliably prevent an older dataset result from being displayed after the page becomes visible.

I would also like to determine whether this behavior can be diagnosed through the Wix Studio developer tools or browser network activity. When the stale content appears, I would like to compare the data request from that page load with a request made after a successful refresh and determine whether Wix is actually returning an older value or whether the correct value is returned but the page continues displaying an older client-side value. That distinction seems important because it would tell me whether the problem is occurring during data retrieval or during the process of binding the retrieved data to the page elements. I have considered logging the dataset values during page initialization, but because the behavior is intermittent, I need a reliable way to capture what the page received at the moment the incorrect value appeared. If Wix Studio provides any recommended debugging approach for dynamic datasets that occasionally display stale collection data, I would appreciate guidance on what events, APIs, console information, or network requests should be inspected. I would also like to know whether there are known considerations when using dynamic pages together with internal navigation and CMS datasets that could explain why a previous value remains visible.

Has anyone else experienced a Wix Studio dynamic page where the CMS contains the latest information but the first page load occasionally displays an older version until the page is refreshed? I am specifically looking for advice on diagnosing this one stale-data behavior rather than general performance or CMS configuration issues. If there is a correct Wix Studio pattern for forcing a dataset to retrieve the latest record when a visitor enters or revisits a dynamic page, I would appreciate an example of how it should be implemented and when the refresh should occur. I can provide details about the dataset configuration, collection permissions, dynamic page setup, browser console output, and the exact sequence of navigation that reproduces the behavior if those details would help. My main goal is to make sure that visitors consistently see the current CMS value when the dynamic page first loads, without requiring them to manually refresh the browser before the updated information becomes visible. Sorry for long post!

2

This matches a known quirk with dynamic datasets on Wix Studio’s client-side page transitions. When a visitor navigates internally (not a full page reload), the page’s dataset component can stay mounted between visits, so $w.onReady() does not fire again and the dataset keeps whatever record it already bound. A hard refresh forces a real reload, which is why the CMS data always looks correct there.

A few things worth checking, in order:

  1. Confirm it is a rebind issue, not a stale server value. Open dev tools Network tab, filter for the dataset’s data request (usually a call to a /_api/ or wix-data endpoint), and compare the payload on a stale load vs after refresh. If the payload already has the new value but the page still shows the old one, it is a client-side binding issue, not caching upstream.
  2. If it is client-side, hook wixLocation.onChange() (or the Router page’s page navigation lifecycle if this is a router-based dynamic page) and call dataset.refresh() explicitly when the page becomes active again. onReady alone will not refire on an in-app navigation to the same widget tree.
  3. If this is a Router-based dynamic page (using router.js, not the native CMS dynamic page binding), check the cache/ttl you are returning in the router response. A cache header set too high will make Wix serve the previous payload for that route until it expires, independent of what is in the CMS.

If you can share whether this is a native Dynamic Page (bound directly to a collection in the editor) or a custom Router page, that would narrow down which of the two fixes applies.

3

The issue is that wixLocation.onChange doesn’t automatically refresh datasets when you navigate between dynamic pages on the same site. The dataset retains its previous query result, so you see stale data until the page actually reloads.

Fix: call dataset.refresh() inside the onChange handler. This refetches from the collection and updates connected elements.

Working pattern:

import wixLocationFrontend from ‘wix-location-frontend’;

$w.onReady(function () {
$w(‘#myDataset’).onReady(() => {
wixLocationFrontend.onChange(() => {
$w(‘#myDataset’).refresh();
});
});
});

Key: the dataset.onReady inside page onReady ensures the dataset is loaded before you wire up the location handler. If you call refresh() before the dataset is ready, it fails silently.

Replace #myDataset with your actual dataset ID. If you have multiple datasets on the page, refresh each one inside the same onChange handler.

This keeps the dataset in sync as users navigate between dynamic pages without a full browser reload.

Reference: Refresh | Velo

4

Thanks, that explanation helps a lot. I’ll check the Network tab and compare the data returned during a stale load with the response after a refresh, because that should help confirm whether the old value is actually coming from the data request or whether the page is keeping an older bound value. The point about internal navigation and the dataset remaining mounted also makes sense given that the issue is more noticeable when moving between pages rather than doing a full reload.

My page is using the Wix Studio CMS dynamic page setup rather than a custom router.js page, so I’m mainly interested in the dataset lifecycle side of this.

5

Good plan on comparing the Network tab payloads, that will settle it quickly. And to answer your last question directly: Webhil’s wixLocationFrontend.onChange + dataset.refresh() pattern is not router.js specific, it hooks client-side navigation in general, so it applies to your native CMS dynamic page setup too. You do not need a router.js page for it to work.

6

Correction to my earlier answer, and to how it was summarised above. wixLocationFrontend.onChange isn’t a general navigation hook. The docs say it only fires when the URL changes without a navigation, which happens inside full-page applications like the Stores product page. A native CMS dynamic item page isn’t one, so the onChange handler most likely never runs there.

Quick test: put a console.log inside the onChange handler, publish, and click from one item to another. If nothing logs, that’s your answer.

On a CMS dynamic page, page code runs again on each page load, including internal navigation. So refresh from onReady instead:

$w.onReady(() => {
$w(“#dynamicDataset”).onReady(() => {
$w(“#dynamicDataset”).refresh();
});
});

Swap #dynamicDataset for your dataset’s ID.

If the page is actually a Stores product page (the thread is tagged wix-stores), onChange is the right hook there. That’s the case it’s documented for.