Last modified: 2010-10-11 15:02:21 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 T27479, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 25479 - Dialogs broken in deployed wikieditor
Dialogs broken in deployed wikieditor
Status: RESOLVED WORKSFORME
Product: MediaWiki extensions
Classification: Unclassified
UsabilityInitiative (Other open bugs)
unspecified
All All
: Normal major (vote)
: ---
Assigned To: Trevor Parscal
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-10-10 12:38 UTC by Derk-Jan Hartman
Modified: 2010-10-11 15:02 UTC (History)
3 users (show)

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


Attachments

Description Derk-Jan Hartman 2010-10-10 12:38:41 UTC
It seems that some of the JS in deployment uses $ now instead of $j and I think that this is related. I get the error 

plugins.combined.min.js:126
TypeError: Result of expression '$j.wikiEditor' [undefined] is not an object.
Comment 1 Roan Kattouw 2010-10-11 12:00:38 UTC
(In reply to comment #0)
> It seems that some of the JS in deployment uses $ now instead of $j and I think
> that this is related. I get the error 
> 
The jQuery 1.4 migration was completed this morning, some 20 hours after your report. Prior to that, the last change to deployed JS was on October 4, and the last change that seems like it could be remotely related was on September 13.

> plugins.combined.min.js:126
> TypeError: Result of expression '$j.wikiEditor' [undefined] is not an object.
That's strange, where are you getting that exactly?
Comment 2 Derk-Jan Hartman 2010-10-11 14:57:04 UTC
I got it yesterday on English Wikipedia, several minutes before the opening of the bug. The problem was at all dialogs and on multiple pages. It seems gone now.
Comment 3 Roan Kattouw 2010-10-11 15:02:21 UTC
Could be caused by site JS maybe, or maybe it's just a fluke (JS file failed to load or something). Closing as WORKSFORME unless and until someone can reproduce.

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


Navigation
Links