Last modified: 2011-03-13 18:05:44 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 T16791, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 14791 - Unique Identifier on [[MediaWiki:Readonlytext]] and WMF Error.html
Unique Identifier on [[MediaWiki:Readonlytext]] and WMF Error.html
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
Templates (Other open bugs)
1.13.x
All All
: Lowest enhancement (vote)
: ---
Assigned To: Tim Starling
: shell
Depends on: 15590 17768
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-11 19:21 UTC by Sam Reed (reedy)
Modified: 2011-03-13 18:05 UTC (History)
3 users (show)

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


Attachments

Description Sam Reed (reedy) 2008-07-11 19:21:35 UTC
Is it possible to get a unique identifier rolled out on [[MediaWiki:Readonlytext]], and one on the WMF Error page (http://svn.wikimedia.org/viewvc/mediawiki/trunk/debs/squid/debian/errors/error.html?view=markup)

Much like the "<DIV id=spamprotected>" that was added to the spam notification page...

Thanks
Comment 1 Chad H. 2008-09-12 22:02:42 UTC
Added one for Mediawiki in r40761. Still need the WMF one done.
Comment 2 Sam Reed (reedy) 2008-09-12 22:19:02 UTC
[http://svn.wikimedia.org/viewvc/mediawiki?view=rev&revision=40763 r40761] adds the mw- prefix
Comment 3 Brion Vibber 2008-09-16 19:55:06 UTC
Hmm, this might need to be updated separately for squids and the patched PHP error display.

Tim, can you check out what the current procedure for updating these error pages is?

* where to update in SVN
* if packages need to be updated/rebuilt
* if packages need to be upgraded/reinstalled

https://wikitech.leuksman.com/view/Squid_error_pages has some old notes for squid, but isn't too clear on how one actually goes about rebuilding the packages. :)
Comment 4 Tim Starling 2008-09-19 02:52:03 UTC
Updating the squid error pages is bizarrely complicated and error prone. You have to update the squid-common package. This means you have to change the release number, but the squid binary package depends on the exact squid-common release, so you have to upgrade that too. So you have to recompile it on a suitable x86_64 server, update the package in APT, then upgrade every squid server. Upgrading will restart the squid daemon, so it needs to be done progressively unless you want the whole site to go down. Experience has shown that it's quite easy to accidentally take down the whole site during such an operation, due to a reduction in performance and cache hit ratio post-restart, leading to a backend overload.

Changing the PHP error messages is thankfully much easier, and I have documented it at <https://wikitech.leuksman.com/view/PHP_error_pages>.
Comment 5 Sam Reed (reedy) 2009-11-06 15:12:37 UTC
Closing as wontfix

No need for this for AWB (original purpose)

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


Navigation
Links