Posted: December 13, 2020 at 11:34 am
Hey guys, we use the “send batch messages” a whole lot each week. But for some reason this week its not working. It might be like alot of plugins after 5.6 update a Jquery issue. I am not smart enough to know about Jquery tho. Replicate: We go to the registrants we want to send a message to and put a checkmark on their name THEN we scroll to bottom and CLICK “Send batch messages (5)” (for when 5 people selected. But now as u can see from the private video screencast, nothing is happening at all. The tab doesn’t spin, the button doesn’t activate, nothing is happening. The video is in private box below. Please advise how we can fix this. thank you |
|
This reply has been marked as private. | |
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? |
|
Okay here is the errors. its the EE-Newsletter-trigger-.js causing the issue. I also made small video example showing that I will paste privately. Hope that helps. Uncaught ReferenceError: dialogHelper is not defined |
|
This reply has been marked as private. | |
I don’t think is from Yes, I know it shows that as calling the function which triggers the error, but I think that’s a symptom rather than the cause. No other errors on that page? Are you using any plugins to alter how JS files load? |
|
Hi, On that same page, the “filtered CSV report” button works perfectly. 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. This is a very important feature to us so we really hope it can be updated soon. thanks |
|
i am creating a staging copy and will give you login details in private reply |
|
This reply has been marked as private. | |
okay I included staging credentials in private reply. That way you can see exactly what we see. I dont know jquery, but I really think it might be just an easy code fix for the Popup that ee tries to trigger when clicking the send batch messages button. Thanks |
|
I didn’t say the issue wasn’t from the WP5.6 update, I simply said I don’t think
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.
Great, but that button doesn’t use JavaScript.
Nothing special is needed here and its expected that you would get the same error if nothing has changed, right?
I can’t fix something I can’t reproduce and the reason I don’t think the issue is with If
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. |
|
Great, that worked perfectly. 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. 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. Instead of having to answer 50 different questions, I feel its better to just include everything I know so that smarter people than me can help find a fix. Thanks |
|
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.
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 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. |
|
The support post ‘Batch messages button not working’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.