What exactly is the difference between a cache purge and a null edit (besides the entry in recentchanges)?
On 6/12/05, Zigger zigger@gmail.com wrote:
The "caching problem" is by design, for performance reasons.
With the parser cache on and current, the same value will always be returned, unless "&action=purge" is appended to a query-style URL.
With the parser cache off or expired, as you found, the browser can request a forced refresh e.g. via Ctrl-F5. Alternatively, browser-side caching can be disabled site-wide for all users ($wgCachePages), per logged-in-user (Special:Preferences), or as a user-preference default ($wgDefaultUserOptions['nocache']).
For an example of using an extension to get dynamic content by time-tricking, see http://www.islandseeds.org/wiki/Test:Fortune and http://meta.wikimedia.org/wiki/MediaWiki_FAQ#How_do_I_add_my_own_dynamic_con...
-- Zigger
On 6/11/05, Wolfe, Jeff wrote:
... The main page of my wiki has the variable {{NUMBEROFARTICLES}} on it. I'm having a problem with multiple client browsers caching this page and not reloading when the variable changes. If I force a reload, the number is rendered correctly. If I change the wikitext, the page is reloaded. Otherwise, I can press F5 all day and not get the latest copy if only the variable has changed. I have verified this with both IE 6.0 and Firefox 1.0.1. I'm running MediaWiki 1.4.1 with a 'recent changes' patch.
Any ideas? Seems like a caching problem with variables. Can I disable caching for this page only? ...
MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l