JS Error: TypeError: d is undefined

[scanbran]

When I an writing or editing a post, I get the above message when I try to use the VISUAL tab. Before a few days ago I could see the WYSIWYG representation of the BBCode using the visual tab in the post editor.

A page where this has happened is at acousticsoundboard.co.uk/thread/edit/679.

This happens all the time now when I'm writing or editing a post.

I am using Mozilla Firefox. I was on version 19.0.2 and this error appeared. I updated to version 20.0 and the error is still there.

I have also tried this using Internet Explorer 10 and get a similar message : JS Error: TypeError: Unable to get property 'success' of undefined or null reference

I am using Windows 7 Home Premium.

Thanks,

Martin

[Chris]

Hi Martin, your Soundcloud plugin would more than likely be the culprit here since it is calling methods on the WYSIWYG (which it shouldn't since they specifically generate AJAX requests). The reason this has only recently started is because a recent push has changed the number of arguments these forbidden methods are expecting.
Disable the plugin in question and if the problem goes away then you'll need to contact Virgil Sovereign

[scanbran]

Thanks EB, that's exactly it - now disabled and the visual editor is working as it should

[Virgil Sovereign]

Hi Martin, your Soundcloud plugin would more than likely be the culprit here since it is calling methods on the WYSIWYG (which it shouldn't since they specifically generate AJAX requests).

The plugin simply inserts hooks into the prototype. If the original process flow is <some event> ==> <call to AJAX function foo()>, the modified flow is <some event> ==> <call to hook, which makes no AJAX calls> ==> <call to AJAX function foo()>. In short, a page with the plugin enabled would generate no more AJAX calls than one with the plugin disabled.

The reason this has only recently started is because a recent push has changed the number of arguments these forbidden methods are expecting.

Aaaaaargh.

Ah well, such is life.

scanbran, I can repair the plugin, but give me until the end of the month. I'm swamped with work.

[Chris]

Apr 14, 2013 8:37:34 GMT -8 Virgil Sovereign said:

Hi Martin, your Soundcloud plugin would more than likely be the culprit here since it is calling methods on the WYSIWYG (which it shouldn't since they specifically generate AJAX requests).

The plugin simply inserts hooks into the prototype. If the original process flow is <some event> ==> <call to AJAX function foo()>, the modified flow is <some event> ==> <call to hook, which makes no AJAX calls> ==> <call to AJAX function foo()>. In short, a page with the plugin enabled would generate no more AJAX calls than one with the plugin disabled.

My apologies Virgil Sovereign, I only eyeballed the code and saw multiple instances of the calls which were generating the errors, I didn't attempt to evaluate their purpose beyond their existence and being the root of the error messages. I've actually employed one or two of those hooks myself but passed on the arguments using apply instead of call if that helps.

There are rumors of a significant upcoming update to the WYSIWYG which could make all this moot so we all wait as well until launch to see what form this eventually takes. Hopefully some kind of developer early warning system is eventually put in place to allow time to head off these bad user experiences.

--
See here for a temporary workaround until author makes an official release.

[scanbran]

Apr 14, 2013 8:37:34 GMT -8 Virgil Sovereign said:

scanbran, I can repair the plugin, but give me until the end of the month. I'm swamped with work.

Thanks for that