Last modified: 2012-05-07 19:49:10 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 T38567, 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 36567 - pseudo "Category:Pages where expansion depth is exceeded" after install 1.20wmf2
pseudo "Category:Pages where expansion depth is exceeded" after install 1.20wmf2
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
1.20.x
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2012-05-06 09:35 UTC by Rical
Modified: 2012-05-07 19:49 UTC (History)
1 user (show)

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

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

Description Rical 2012-05-06 09:35:32 UTC 
* In fr.wikisource.org, for May 3rd 2012 some pages are put in a pseudo "Category:Pages where expansion depth is exceeded".
* This appears after install 1.20wmf2 on May 1st 2012. 48 pages was put in the pseudo category along 3 days.
* All pages use the <pages> tag like <pages index="Mallarmé - Poésies, 1914, 8e éd.djvu" from=156 to=157 header=1 />.
* First discussion is here with the living drop down list of pages with their dates :
http://fr.wikisource.org/wiki/Wikisource:Questions_techniques#Pages_where_expansion_depth_is_exceeded
Comment 1 Mark A. Hershberger 2012-05-07 17:36:13 UTC 
Is the problem that the use of the <pages> tag causes this category to be used?
Comment 2 Rical 2012-05-07 19:49:10 UTC 
Marc corrected the template which generate the pseudo category. Then the bug never exists. I'm sory to disturb you. I close it as RESOLVED INVALID.
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