Last modified: 2008-01-16 07:25:47 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 12633 - Bot-created articles appear in Special:Recentchanges by default
Bot-created articles appear in Special:Recentchanges by default
Status: RESOLVED DUPLICATE of bug 12611
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal major with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2008-01-15 00:06 UTC by Minh Nguyễn
Modified: 2008-01-16 07:25 UTC (History)
1 user (show)

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


Description Minh Nguyễn 2008-01-15 00:06:50 UTC
I'm receiving reports that bot-created articles have begun appearing in [[vi:Special:Recentchanges]], with hidebots=1. I cannot reproduce this on the Vietnamese Wiktionary, so the problem appears to be confined to the Vietnamese Wikipedia. Some bots have stopped making edits, pending this bug. The two bots that have encountered this issue primarily make edits to User talk: pages, so Bug 12582, a recent shell fix involving user talk pages, may be related somehow.
Comment 1 Tran Vinh Tan 2008-01-15 07:26:43 UTC
I tested by creating a article in main namespace, it also appeared in recent changes.
Comment 2 Brion Vibber 2008-01-16 07:25:47 UTC
Think this was bug 12611

*** This bug has been marked as a duplicate of bug 12611 ***

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