Last modified: 2009-09-26 19:17:13 UTC
English Wikinews employs the following DPL on the main page to list recent news stories: <nowiki> <DynamicPageList> category=published notcategory=No publish notcategory=Archived notcategory=AutoArchived stablepages=only count=20 addfirstcategorydate=true ordermethod=categoryadd namespace=0 suppresserrors=true showcurid=true </DynamicPageList> </nowiki> This should list, in order of publication, the most recent 20 published articles that have been sighted with FlaggedRevisions. This fails in some unpredictable ways, with articles published several days ago suddenly appearing nearer the top of the list and attributed to the incorrect date. There are two suspected causes of this: 1) Renaming an article resets when it was added to the Published category. 2) Edits by users who cannot sight an article to remove the article from the Published article impact when the article is recorded as being in the published category. Example, they remove the {{publish}} template, thus creating an unsighted revision, their change is reverted and the new version is sighted. However, DPL appears to see the version without {{publish}} despite the 'stablepages=only' qualifier that should make it ignore all unreviewed versions.
Suspected cause #1 - I might be wrong, but i was under the impression that that was fixed long ago if memory serves. Looking through articles that were moved yesterday, but have categories with a categoryadd timestamp back in 2006, seems to suggest that this is not an issue. Suspected Cause #2 - this is an issue. It would be nice if the dpls that do only stable pages, used the category add date from the stable version. Page blanking vandalism has been a big issue at wikinews because of this. Cause #3 - not listed in the original bug as a suspected cause, but one of the major causes: a bunch of pages at the same time as this bug had their dates change when {{DEFAULTSORTKEY}} was added. Ideally changing the sortkey of a category should not change the categoryadd timestamp. (See Bug 16287). I have a feature request that well wouldn't fix these issues, would help deal with them. I am filing it as a seperate bug, as this bug is already about several different issues. See bug 20378
Mostly a duplicate of Bug 20813, and anything that wasn't was a duplicate of Bug 16287 *** This bug has been marked as a duplicate of bug 20813 ***
