Last modified: 2005-07-14 05:40:25 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 T3926, 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 1926 - Server error causes javascript and CSS failure
Server error causes javascript and CSS failure
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
PC Windows 2000
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: javascript
  Show dependency tree / graph
 
Reported: 2005-04-19 16:24 UTC by Alphax
Modified: 2005-07-14 05:40 UTC (History)
0 users

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

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

Description Alphax 2005-04-19 16:24:22 UTC 
Sometime about 15:30 UTC on 2005-04-19, I got the following error appearing on
pages served to me by en.wikipedia.org:

<br />
<b>Warning</b>:  gzuncompress(): data error in
<b>/usr/local/apache/common-local/php-1.4/includes/memcached-client.php</b> on
line <b>868</b><br />

A screenshot is located at
<http://en.wikipedia.org/wiki/Image:Alphax-20050419-bug.png>

Sometime around 16:00 UTC, the text disappeared, but the customizations provided
by my monobook.js and monobook.css appeared to have been lost. Firefox was also
reporting javascript errors, such as the one below:

Error: syntax error
Source File:
http://en.wikipedia.org/w/index.php?title=User:Alphax/monobook.js&action=raw&ctype=text/javascript&dontcountme=s
Line: 1
Source Code:
<br />

so I decided to see if the problem was apparant in Internet Explorer. It was not.

Is Firefox or Mediawiki to blame?
Comment 1 Tim Starling 2005-04-19 16:37:56 UTC 
The first problem should have been fixed at 16:04, and the second at about
16:17. Is it still happening?
Comment 2 Alphax 2005-04-19 16:43:45 UTC 
OK, it's fixed now. Persistance must have been browser cache. Just out of
interest, what was the cause?
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