Last modified: 2010-05-15 15:42:53 UTC
"$wgUseFileCache = true;" The functionality of the file caching works fine but limits the eze of extensions that create dynamic content. Logged in user: will pull the content directly from the database and generate the content directly logged out user: will pull the content from the local cache and will contain the "snapshot" of what the dynamic content was the last time the page edit was submitted. DPG2 doesn't work with caching! Could you find a way to create a stop cache value in extensions such as DPG2 or look into making some kind of __NOCACHE__ magic word?
A __NOCACHE__ magic word would be prone to abuse. In most cases, parser extensions ought to use the ParserOutput object to work around the caching problem, if possible. In other cases, the extension might be able to disable the cache in particular instances (this can be done within the rendering function, through the $parser reference), otherwise the users of the extension should accept that the output won't be 100% up-to-the-minute.
The extension should be able to mark the page non-cacheable already, as I understand it. I'm going to go ahead and dupe this to bug 7998; if DPL2 or whatever needs to be adjusted, that's the place. *** This bug has been marked as a duplicate of 7998 ***
