Page MenuHomePhabricator

Javascript not working in Arabic Wiktionary
Closed, ResolvedPublic

Description

Hi, try editing any page in the Arabic Wiktionary, you'll notice that the Edit toolbar does not show and the Edit toolbox isn't working as well.


Version: unspecified
Severity: normal

Details

Reference
bz38522

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 12:51 AM
bzimport set Reference to bz38522.
bzimport added a subscriber: Unknown Object (MLST).

This should now be fixed. See the following diffs for further info:

http://ar.wiktionary.org/w/index.php?title=%D9%85%D9%8A%D8%AF%D9%8A%D8%A7%D9%88%D9%8A%D9%83%D9%8A:Common.js&diff=prev&oldid=509140

http://ar.wiktionary.org/w/index.php?title=%D9%85%D9%8A%D8%AF%D9%8A%D8%A7%D9%88%D9%8A%D9%83%D9%8A:Monobook.js&diff=prev&oldid=509141

http://ar.wiktionary.org/w/index.php?title=%D9%85%D9%8A%D8%AF%D9%8A%D8%A7%D9%88%D9%8A%D9%83%D9%8A:Monobook.js&diff=prev&oldid=509142

The root cause of the problem was bad copy-paste (diff #2); someone had tried pasting code from the local MediaWiki:Common.js into MediaWiki:Monobook.js and failed; as a result, there was a superflous function call and two superflous braces and one undefined function, which caused problems with JS loading. I copied the function from the local MediaWiki:Common.js page into MediaWiki:Monobook.js and fixed some issues in MediaWiki:Common.js and MediaWiki:Monobook.js and now I'm able to see the standard edit buttons on ?action=edit.

In the future, when reporting JS issues, please include the following information in your report:

  • your browser and its version
  • your skin (Vector, Monobook, etc.)
  • your language (usually this shouldn't matter, but there might be some scripts which are executed for certain languages only)
  • your login status; are you logged in to the wiki (like the above, this normally shouldn't matter, but you never know...)

Please check to see if the problem has been fixed; if it's still happening, try refreshing your cache (CTRL+F5 on most browsers) and maybe logging out and then logging back in. If it is *still* happening, please reopen this bug.

It's fixed. Thanks for the thorough response.