Last modified: 2010-12-22 16:17:32 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 T28386, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 26386 - Categorizing pages using parserfunctions
Categorizing pages using parserfunctions
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
ParserFunctions (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
http://www.mediawiki.org/wiki/Extensi...
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2010-12-22 00:07 UTC by TeleComNasSprVen
Modified: 2010-12-22 16:17 UTC (History)
3 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description TeleComNasSprVen 2010-12-22 00:07:53 UTC 
I'd like to see a method introduced where pages using certain ParserFunctions are able to have category information about that ParserFunction. For example, placing {{catparser:__NOINDEX__}} on a certain page would categorize it under some [[:Category:Page using __NOINDEX__]] much as how the current __HIDDENCAT__ magic word is categorizing pages into [[:Category:Hidden categories]].
Comment 1 Bawolff (Brian Wolff) 2010-12-22 07:38:05 UTC 
Wasn't there a plan to add all these parser functions to the page props table, and then have an api module to query them? I think that would solve the problem you're trying to solve.

Also are you aware of [[Category:Noindexed_pages]] (I know you only used NOINDEX as an example, and are more after the general case, but i thought i should mention it).
Comment 2 db [inactive,noenotif] 2010-12-22 16:17:32 UTC 
(In reply to comment #1)
> Wasn't there a plan to add all these parser functions to the page props table,

bug 14685

> and then have an api module to query them?

bug 24484
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links