[Plugin: The Events Calendar] plugin error = Bug in menu of WordPress

Yes, I had to patch this version, as well to get it to work again.

All occurrences of “on()” needed to substituted with “bind()”

4 of them were in
the-event-calendar/resources/events.js
1 was in
the-event-calendar/resources/jquery.pjax.js

These showed up with obvious red error messages in the Chrome Developer console.
roblagatta, is Chrome supported?

Alright bguthro, thanks for the clarification. Got a dev taking a look at this shortly to confirm what’s up.

The plugin is Chrome supported, yes. Had you updated to 2.0.11 to find these problems, or were they still in 2.0.10? There was an issue with the Jquery 1.9 release earlier last week that could have had an impact here, but should be resolved if you updated.

roblagatta, I honestly couldn’t tell you, since I wasn’t the one who upgraded the plugin – I just got the call when it broke.

The last time I fixed it would have been whatever version was available at the time of my original comment, then again a few days ago. The person who upgraded it simply saw in the wp-admin plugins panel, that updates were available, and upgraded.

Sadly, there is no way to roll back an update.

I have advised her to not update this plugin unless I have time to debug and fix issues, since 2 updates have shown it to be an unreliable process prone to breaking the rest of her website.

For me problem comes with the 2 last upgrades.
My version is 2.0.11

Hi everybody.

Where are you guys seeing this error, i.e. what events page? Or, does it happen when you do something like navigate months in the calendar? Can anyone post a link and instructions on how to reproduce? I’m not seeing it at all running the latest 2.0.11 version of our plugin.

Thanks,
Jonah

I can’t break the site for the purposes of debugging – but the site in question can be found at https://www.iamers.org

It is running 2.0.11, and it needed the modifications mentioned above in order to not throw javascript errors, and break other things, like menus, and the front page image.

Bug is in homepage. Menu has a problem (all is shown, menu and submenu, and impossible to close them).
And error code in shown in firefox console.

I use free theme : Black and White (here : https://www.hhcolorlab.com/inspire/websites_for_photographers/black_and_white)

@bguthro – I don’t see any errors related to our plugin. You’ve got some other javascript errors in place that are unrelated to our plugin. Here’s a screenshot of the Chrome console: https://cl.ly/image/0P0j0P252P2e – I would try and sort these out first. Also, you’re running a fairly old version of jQuery (1.4.2) so you might try updating that to the most recent WordPress version (1.8.3). That may help.

@pppplus – you’ve also got an js error that is unrelated to our plugin. You should clear this up first. Here’s a screenshot of the Chrome console: https://cl.ly/image/3S1A233W0Y0r

– Jonah

I do not understand your answer.
Where do you see error on my website ? I don’t post my url here.

@pppplus – sorry, I thought the link you posted above (https://www.hhcolorlab.com/inspire/websites_for_photographers/black_and_white) was your website.

– Jonah

no, it is the site where I download the theme.
So, you can test with this theme, and see there is a problem between theme and your plugin.

@jonahcoyote – I don’t have any errors because, as I mentioned before, I fixed them with the s/on/bind/g fix.

@jonahcoyote – The version of jQuery I am running is whatever ships stock with WP 3.5 (the latest available.) It seems a bit risky to other functionality to upgrade that.

Plugins to a platform should conform to the restrictions of that platform, and not require additional non-standard configuration.

If you require a particular version of jQuery, you should ship this as part of the packaging, or make it clear to the user that you require a minimum version in order to not break other parts of the WP platform.

hmm… the WP version installed is 1.8.3 – I guess I’ll have to look around to try to determine why 1.4.2 is being loaded, if that is what you’ve determined.

sigh…the theme was explicitly loading an old jQuery, unbeknownst to me.
Sorry for the misplaced accusations.