Board Thread:Support Requests - Getting Technical/@comment-5879271-20191222072741/@comment-9605025-20191222082028

Would you mind letting us know what they say in their reply?

Unfortunately, I don't think there are any ready-made alternatives available for FANDOM wikis. You could ask on the dev wiki for a JS script to be made but I personally don't think it would be worth the effort unless we hear back that the change was intentional.

Regarding caching, there are multiple caches that do different things. Typically, when an extension talks about caching with regards to its own features, it is referring to its own cache that uses its own caching rules. The page, however, is subject to the page cache. The content on the page is re-parsed (i.e. freshly determined) only when the page cache is cleared. Even if the extension cache has reached it's own refresh time, the page won't know until it checks at the page refresh time. It is a similar "issue" with DPL. Let's say the page cache was just cleared and the RandomSelection cache clears 10 seconds later. The next time the page checks to see what should be rendered (i.e. the page cache is cleared), RandomSelection will give it the new content. However, if the page doesn't check until 24 hours later (for example), then it won't get the new content until 24 hours later; even though the new content is ready sooner. The reason why it works when previewing is that previewing edit changed always renders a new version of the page. However, that version isn't saved and the page cache is not cleared. When you actually publish the edits, the page cache is cleared. The page cache is cleared periodically as well as on-demand.

Using your browser's refresh, however, does not clear the page cache; it clears your browser's cache. When this happens, you browser requests a new copy of the page from the server. However, if the page cache has not yet been cleared, then the new copy your browser gets is no different from the one you tried to clear. So, in summary, seeing a change reflected on the page requires at least 3 (there could be even more we haven't covered) different caches to be cleared in the proper order. In order:
 * 1) Extension
 * 2) Page
 * 3) Browser