Last modified: 2010-05-15 15:42:53 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 7999 - __NOCACHE__ magic word
__NOCACHE__ magic word
Status: RESOLVED DUPLICATE of bug 7998
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
1.8.x
PC Windows XP
: High enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-11-20 19:50 UTC by Ashley "Shlee" Hull
Modified: 2010-05-15 15:42 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Ashley "Shlee" Hull 2006-11-20 19:50:30 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?
Comment 1 Rob Church 2006-11-20 21:51:21 UTC
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.
Comment 2 Brion Vibber 2006-11-29 21:52:36 UTC
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 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links