Last modified: 2007-05-27 06:32:17 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 2401 - Deprecated, moved and other wikis with locked database
Deprecated, moved and other wikis with locked database
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-06-13 15:04 UTC by lɛʁi לערי ריינהארט
Modified: 2007-05-27 06:32 UTC (History)
1 user (show)

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


Description lɛʁi לערי ריינהארט 2005-06-13 15:04:06 UTC

The user interface / configuration of these wikis is iritating because it is (as
for [[tokipona:]]) neither possible to create an account, edit etc.

At least the [[MediaWiki:Sitenotice]] should inform about this.

I want to mention this here but probably it is another bug related to the
interwiki bot.
Because some time past after the last changes at these wikis interlanguage links
can cause conflicts.
I am not aware if pywikipediabot handles this or not.

Regards Reinhardt [[user:gangleri]]
Comment 1 Antoine "hashar" Musso (WMF) 2007-05-27 06:32:17 UTC
pywikipediabot should raise an exception about the database being locked.
We still want user to be able to login when the database is temporally
Locked wiki have a main page explaining it got locked or a sitenotice already.

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