In digest EGHCTWIJKG, the 'show live items only' seems to be over-zealous.
If it is checked, no items show up. If it is unticked, all four items show up.
In fact, the 11:45 item is an unbooked, and available appointment, and should show up, whilst the others should stay hidden. This has worked in the past. Not sure what the problem is now.
But I also note that the feed itself appears to be cached on your server as it doesn't reflect a name-change to items that I made yesterday.
Caching affects 'show live items only'?
Thanks for posting this, Susannah.
I am seeing the exact same problems with the 'show live items only' filter being broken (it just hides everything). I've also noticed data updates taking way too long to show up in the feed, so your observation about the caching issue seems spot on.
Hopefully, the administrators can fix the logic and reduce the cache time soon.
Regards
Think caching delays real-time updates, causing old or outdated data to appear even when “show live items only” is selected.
They may believe the cache prevents immediate reflection of new items, questioning whether live data bypasses cached content or needs manual refresh.
Hopefully, the administrators will fix the logic and reduce caching soon.
Best regards
Does caching impact the functionality of the show live items only feature, potentially causing outdated or non-live items to appear?
Caching can sometimes interfere with the “show live items only” feature by displaying outdated or previously stored data instead of real-time results. When cached content is served, the system may not refresh instantly, causing delays in showing current live items. Clearing or adjusting cache settings usually helps restore accurate, up-to-date visibility of live listings.
Caching can influence the “show live things only” highlight by showing put away, obsolete information instep of real-time upgrades. When cache is empowered, as of late changed or recently included live things may not show up quickly, causing delays or irregularities in what clients see.
You must log in to post.