robchur wrote:

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 ***