Last modified: 2013-10-29 08:31:43 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 T58299, 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 56299 - $wgReadOnly is not being signalled
$wgReadOnly is not being signalled
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
ReplaceText (Other open bugs)
master
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2013-10-29 07:36 UTC by Siebrand Mazeland
Modified: 2013-10-29 08:31 UTC (History)
4 users (show)

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

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

Description Siebrand Mazeland 2013-10-29 07:36:48 UTC 
Today we were migrating the translatewiki.net site to a new server. We'd set $wgReadOnly. We forgot to notify Raymond. Raymond happily was able to use Special:ReplaceText without being aware the site was read-only.

User story:

As a user of Special:ReplaceText, I want to be notified of a MediaWiki instance being read-only, so that I can better assess if I should try to make changes now or now.
Comment 1 Nemo 2013-10-29 07:40:58 UTC 
Does the extension manage to add those changes to the job queue even though the wiki is read-only? ([[mw:Manual:$wgReadOnly]] is quite generic and has a note "Some of your installed extensions may write data nonetheless".)
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