Last modified: 2013-10-06 18:30:30 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 T56770, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 54770 - Semantic Forms show on select broken in current master (problem with dynatree javascript)
Semantic Forms show on select broken in current master (problem with dynatree...
Status: VERIFIED FIXED
Product: MediaWiki extensions
Classification: Unclassified
SemanticForms (Other open bugs)
master
All All
: Unprioritized normal (vote)
: ---
Assigned To: Yaron Koren
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-29 21:28 UTC by Jamie Thingelstad
Modified: 2013-10-06 18:30 UTC (History)
0 users

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


Attachments

Description Jamie Thingelstad 2013-09-29 21:28:00 UTC
Just did a fresh pull of SemanticForms and the 'show on select' functionality seems to not be working right. I think this is probably a Javascript error in the new dynatree code added in d17cdb5e04f382614e1590500f3ac85de94626f0. 

The following error is shown in Javascript console:

Exception thrown by ext.semanticforms.dynatree: 'undefined' is not a function (evaluating 'nodeSelection.dynatree("getTree").getSelectedNodes()')

Reverting back to 47fbce52bbd9f1c466162b264e5ab38141d96014 restores the show on select functionality, further pointing to the new dynatree feature.

Found error at

http://wikiapiary.com/w/index.php?title=Online_Privacy_Wiki&action=formedit

However have reverted my site back so the error doesn't display now.
Comment 1 Yaron Koren 2013-09-30 04:10:30 UTC
Sorry about that - it's actually not just "show on select" that's broken, but everything Javascript-related, as a result of this new patch. It's a known issue, and hopefully it'll be fixed very soon - if it can't be fixed, I'll have to just revert the whole patch.
Comment 2 Yaron Koren 2013-10-01 13:19:03 UTC
I believe this is fixed now, thankfully.
Comment 3 Jamie Thingelstad 2013-10-06 18:30:30 UTC
Pulled and verified.

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


Navigation
Links