Last modified: 2013-01-02 09:24:48 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 42944 - [Regression] Watchlist fails: "Uncaught TypeError: mw.messsage is not a function"
[Regression] Watchlist fails: "Uncaught TypeError: mw.messsage is not a funct...
Product: MediaWiki
Classification: Unclassified
Watchlist (Other open bugs)
All All
: Highest major (vote)
: ---
Assigned To: Krinkle
: code-update-regression
Depends on:
  Show dependency treegraph
Reported: 2012-12-11 08:24 UTC by Niklas Laxström
Modified: 2013-01-02 09:24 UTC (History)
6 users (show)

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


Description Niklas Laxström 2012-12-11 08:24:29 UTC
Looks like regression in 1.21wmf6.

Js error: Uncaught TypeError: Object #<Object> has no method 'messsage'
Comment 1 Nemo 2012-12-11 08:56:39 UTC
Yes, same on monobook.

Data e ora: 11/12/2012 09:55:37
Errore: TypeError: mw.messsage is not a function
File sorgente:
Riga: 168
Comment 2 Andre Klapper 2012-12-11 15:02:30 UTC
My wild guess: 
"messsage" is likely a typo (hence mediawiki/core/resources/mediawiki/mediawiki.js:297 cannot be found?), but no recent changes in 
  core / resources / /
so maybe some other changes made reaching the Error condition in the calling code suddenly more likely.
Comment 3 Alex Monk 2012-12-11 17:01:31 UTC
Gerrit change #38113 fixes this 'messsage' error, but it won't solve the issue of watchlisting things failing as this is actually in the code to display errors. 
(msg = mw.messsage( 'watcherrortext', link );)
Comment 4 Niklas Laxström 2012-12-11 18:15:53 UTC
I cannot reproduce it anymore btw. Too bad I didn't take the whole backtrace.
Comment 5 Andre Klapper 2012-12-11 18:21:14 UTC
[Decreasing my tentative "Highest prio" and "blocking 38865" in that case. Please increase again after reproducing.]
Comment 7 Krinkle 2013-01-02 09:22:08 UTC
It can only be reproduced in case of an API error. The code is still in 1.21wmf6, the fix needs to be backported as it will cause an Uncaught Exception.

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