Last modified: 2011-04-14 15:13:26 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T12561, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 10561 - Allow transclusion of Special:Random and related pages
Allow transclusion of Special:Random and related pages
Status: NEW
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
1.11.x
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-07-13 08:33 UTC by Matt
Modified: 2011-04-14 15:13 UTC (History)
2 users (show)

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


Attachments

Description Matt 2007-07-13 08:33:54 UTC
I have been working on several wikis lately, and I have come across a case where I want to transclude a random page (either from mainspace, all namespaces, or a specific namespace). This shouldn't be too hard to do, with some minor changes to the parser. I would have no clue how to implement it however.
Comment 1 Rob Church 2007-07-13 09:38:20 UTC
"Related pages" refers to what?

I'm not sure it's a great idea to encourage people to include "random" content into another page, and it wouldn't have the anticipated effect of injecting random content on each view, due to the parser cache.
Comment 2 Brion Vibber 2007-07-13 14:08:32 UTC
Sane behavior for 'random' stuff like this is kind of tricky to handle correctly.
If we had something time-based with expiration (and re-cache and refresh links on next change), it might be fairly sensible though.
Comment 3 Matt 2007-07-13 23:44:28 UTC
By related pages, I mean the subpages etc. Basically, all the special pages that generate random content.

It would have to have a cronjob or something similair to expire the cache every X units of Y, perhaps the page table could be changed to have a "expiry" value, to make it auto purge? Not sure how this would be set though, probably a sysop function, however implementing the expiring shouldn't be too hard.

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


Navigation
Links