Support

December 13, 2020 at 1:30 pm

Hi Jarred,

It most likely is from the WP5.6, but the batch functionality is working fine on my test sites which means its most likely another plugin throwing a JS error on the page which is then prevent EE’s JavaScript from running.

In Chrome Dev tools check the Console, does is show any error when you load the registration list table?

Leave the console open and select a registrant, then click the batch button, any errors in the console then?

December 15, 2020 at 2:58 pm

no I am not using any plugins to alter JS. It’s pretty clear to me that 5.6 update is the cause.

I didn’t say the issue wasn’t from the WP5.6 update, I simply said I don’t think ee-newsletter-trigger.js is the actual cause of the error.

But that’s why SO MANY plugins are releasing updates for Jquery reasons. You can search problems with 5.6 and you will find LOTS of plugins and themes have had issues and required updates.

Thanks but I’m well aware of the issues WP 5.6 has brought on for other plugins, I’ve posted about it a few times on the forum already. The updates required aren’t for ‘special jQuery’ etc, they simply update to use the ‘new’ (which aren’t so new)/’correct’ functions.

In short, WordPress 5.5 stopped the ‘jQuery-migrate’ script from loading by default. jQuery-migrate held a lot of functions that have been deprecated/removed from the jQuery library to allow plugins to continue to function whilst giving them the chance to update, a lot of plugins simply didn’t.

WordPress 5.6 updated to jQuery 3, which now doesn’t have those functions and the migrate script for it doesn’t include them either. Plugins are trying to use those functions and they don’t exist, hence the issues.

So, again, I’m well aware of the issues at hand.

On that same page, the “filtered CSV report” button works perfectly.

Great, but that button doesn’t use JavaScript.

It’s only the SEND batch messages button that is having the problem. Probably becuase it requires special jquery to make that POPUP form appear where we select global template and write our message. I tested it again and the errors that I get are still the exact same errors that I shared in that private video above.

Nothing special is needed here and its expected that you would get the same error if nothing has changed, right?

This is a very important feature to us so we really hope it can be updated soon. thanks

I can’t fix something I can’t reproduce and the reason I don’t think the issue is with ee-newsletter-trigger.js is becuase the batch feature is working just fine on my test sites, most now run 5.6, some 5.5.3.

If ee-newsletter-trigger.js used a deprecated/removed function I’d get issues on those sites and I don’t, so something on your site is doing something unexpected here.

i am creating a staging copy and will give you login details in private reply

Thanks, as suspected, this isn’t an issue with Event Espresso, it’s from the ‘Products By Attributes & Variations for WooCommerce’ plugin which is replacing the version of jQuery UI on your site with an older one, which then throws errors when other plugins try to use it.

I’ve de-activated that plugin on the staging site you created and now the batch message works fine.

December 16, 2020 at 4:54 am

Not sure why your reply was so hostile. I was only doing my best to help you find a solution to why the ee button didn’t work.

It seems you assumed that by me simply telling you what I know about the issue was the same thing as saying you didn’t know something.

I’m sorry if my reply came across as hostile, it wasn’t intended as such. Nor did I assume you thought I didn’t know anything around the issue, although it did imply EE needed some kind of special code to run which isn’t the case.

I believe in being honest and direct with all my replies, if I’m not it leaves too much open to interpretation and we end up going around in circles. If that comes across as hostile then generally it’s not intended.

Maybe read the support tickets as if the person on the other end is just sharing as much info as possible to try and find a solutuion for their business.

That’s exactly how I take each and every thread/reply on the forums, the more you can provide on the issue itself the better.

To explain, you mentioned searching around for what other plugins are doing with regards to the WP5.6 update so I explained that I’m aware of the issue and the reason for other plugins being forced to update with WP5.6 (as have we for a .unload() function use that we missed).

Without explaining the issue a little and showing that I’m not simply dismissing your comment I then can’t tell you “It’s not that file” as you’ll have no idea why. With the explanation above you can understand why and not just the what.

In any case, again I’m sorry you felt my reply was hostile but I’m glad it’s now working, if you run into any further issues please let us know.