Last modified: 2013-11-25 16:06:29 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 18478 - Time-dependent conditionals (#ifeq, #switch, etc.) can leave link tables inconsistent
Time-dependent conditionals (#ifeq, #switch, etc.) can leave link tables inco...
Status: NEW
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
1.15.x
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
http://commons.wikimedia.org/w/index....
:
: 16243 37001 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-04-15 17:56 UTC by Ilmari Karonen
Modified: 2013-11-25 16:06 UTC (History)
8 users (show)

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


Attachments

Description Ilmari Karonen 2009-04-15 17:56:31 UTC
By using the conditional parser functions #ifeq, #ifexpr or #switch together with #time (or with time-dependent magic words such as CURRENTDAY), a page can be made to parse and render differently at different times.  However, the link tables (pagelinks, imagelinks, templatelinks and categorylinks) will only contain links that were present when the page was parsed.

This is closely related to bug 14404, but I'm filing this separately since the proximate cause is different, and since I suspect they'll need separate fixes.

I particular, this can cause cascading protection to fail unexpectedly if such time-dependent conditionals are used on the protected page.  Of course, the workaround is to just not do that, but not all users may know that.  (And, unfortunately, many of the pages most likely to need cascading protection are also the ones most likely to benefit from time-dependent parsing.)
Comment 1 Ilmari Karonen 2009-04-15 18:01:51 UTC
Actually, changing component from Extensions / ParserFunctions to MediaWiki / Page rendering, since I believe the same problem can also be caused by plain transclusion (with time-dependent template names) without using ParserFunctions.
Comment 2 Umherirrender 2012-08-12 16:46:34 UTC
*** Bug 16243 has been marked as a duplicate of this bug. ***
Comment 3 Liangent 2012-08-12 16:57:13 UTC
Can we update links tables every time a new ParserOutput is generated and differs from current links table data (that is like, api.php?action=parse&forcelinkupdate is always used)? A similar thing is already there to update category info.

This can more or less resolve bug 34039, bug 31628 etc.
Comment 4 db [inactive,noenotif] 2012-09-16 07:48:41 UTC
*** Bug 37001 has been marked as a duplicate of this bug. ***
Comment 5 Joe Decker 2013-04-30 00:28:12 UTC
In terms of effects, note that we actually have bot tasks, and discussions around same, on ENWIKI to work around this, see, for example: http://en.wikipedia.org/wiki/Wikipedia:Bots/Requests_for_approval/Joe%27s_Null_Bot

Which is pretty kludge, and we may wish to expand that to 1K articles/day getting bot-bumped.

A workaround, such as expiring category tables after a day would address that particular need, as would a general fix (such as that Liangent proposes.)

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


Navigation
Links