Last modified: 2010-08-07 18:50:34 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 T26484, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 24484 - Add prop=pageprops module
Add prop=pageprops module
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
API (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Roan Kattouw
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-22 08:54 UTC by Sam Reed (reedy)
Modified: 2010-08-07 18:50 UTC (History)
5 users (show)

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


Attachments

Description Sam Reed (reedy) 2010-07-22 08:54:12 UTC
As above
Comment 1 Sam Reed (reedy) 2010-07-22 09:07:41 UTC
<Reedy> Also, for the page props, there's going to be no way to say "these are all the possible properties" is there? As I guess it's not stored...
<Reedy> Unless we add more globals (ugh..) and let extensions register any they may add, aswell as doing the core ones somewhere...
<RoanKattouw> No, those aren't being registered
<Bryan> you can also make it a parser static variable is you don't want to use a global :)
<Bryan> or even an instance variable

^ something to be thought about
Comment 2 X! 2010-08-06 23:40:33 UTC
What about doing a SELECT DISCINCT pp_propname FROM page_props; to fill the list of properties? It's hacky, but it'd work. If not, I think that a $wgPageProps array might be the best option, and it would match the current code conventions.
Comment 3 Roan Kattouw 2010-08-07 10:32:18 UTC
I think $wgPageProps would be much better than running that SELECT DISTINCT query over and over. We also do this for e.g. user rights.
Comment 4 X! 2010-08-07 18:50:34 UTC
r70638

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


Navigation
Links