Last modified: 2009-04-27 08:17:52 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 18491 - Runtime Error on Line 13 on "My watchlist"
Runtime Error on Line 13 on "My watchlist"
Product: MediaWiki
Classification: Unclassified
Watchlist (Other open bugs)
PC Windows XP
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2009-04-17 05:56 UTC by Robert
Modified: 2009-04-27 08:17 UTC (History)
1 user (show)

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


Description Robert 2009-04-17 05:56:57 UTC
In Wikipedia, a few days ago I began receiving errors every time I refresh "My watchlist" - IE6 Windows XP. This does not occur on other Wikipedia pages.

A Runtime Error has occurred.
Do you wish to Debug?

Line: 13
Error: Expected identifier, string or number
Yes   No   
Comment 1 Niklas Laxström 2009-04-27 06:54:30 UTC
Too few details, needs the script filename, or at least I am assuming that this is a JavaScript error, which might be specific to English Wikipedia. Please test in other projects and/or try to provide more information about the error and re-open the bug.
Comment 2 Niklas Laxström 2009-04-27 06:55:45 UTC
Or, alternatively paste the affected line from the page html source, if that is it.
Comment 3 Robert 2009-04-27 08:17:52 UTC
It quit failing about 2 days ago. I though you had fixed it. Will reopen if it comes back.

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