Last modified: 2011-03-13 18:06:18 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 4919 - Dated categories emptied
Dated categories emptied
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
PC Windows XP
: Lowest normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-02-08 20:48 UTC by Andreas Vilén
Modified: 2011-03-13 18:06 UTC (History)
0 users

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


Description Andreas Vilén 2006-02-08 20:48:59 UTC
The above url is just an example. All dated categories have had their content moved to the latest category, the 
same happened in January. This is an annoyance since at least Swedish Wikipedia uses this to keep track of images 
with bad licence info. I don't know what's causing this and I guess it can't be reverted, but at least the bug can 
be fixed so it won't happen again?
Comment 1 JeLuF 2006-02-08 20:56:40 UTC
The template uses [[Kategori:Bilder som saknar upphovsrättslig information
{{CURRENTYEAR}}-{{CURRENTMONTH}}]] to put the images into categories. This is
evaluated when viewing a page, not when saving is. So when someone looks at the
image, it moves itself to the new category. Works as designed. 

Use subst: to evaluate the date on save.
Comment 2 Andreas Vilén 2006-02-08 22:01:11 UTC
OK, but it's weird that all images were moved at the same time... Thanks for the answer anyway, I'll inform the 
svwiki community.

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