|
sylvinic
|
September 16, 2020 at 6:14 am
Hi,
I got an email that was a critical error with this plugin and I am wondering if that is why when I click “create ticket”, it refreshes but no new ticket line appears.
This is my first time using this plugin, so any help you can provide would be great!
|
|
Tony
|
September 16, 2020 at 6:45 am
Hi there,
Did the email show the error that was thrown?
IF you click ‘Create Ticket’ and the page just refreshes that usually a good indication that there is a JavaScript error being thrown on the page. If you open up Chrome Dev Tools (or similar) on the event editor and look in the ‘console’ can you see any errors?
|
|
sylvinic
|
September 16, 2020 at 10:54 am
Yes, this is what it said:
Error Details
=============
An error of type E_COMPILE_ERROR was caused in line 89 of the file /home/hamptonn/public_html/wp-content/plugins/event-espresso-decaf/core/helpers/EEH_Autoloader.helper.php. Error message: require_once(): Failed opening required ‘/home/hamptonn/public_html/wp-content/plugins/event-espresso-decaf/core/helpers/EEH_Template.helper.php’ (include_path=’.:/opt/cpanel/ea-php74/root/usr/share/pear’)
|
|
Tony
|
September 16, 2020 at 12:40 pm
That error is from EE4 decaf, but on your site you have the full version of the plugin (as expected). Did you get that error when you switched over from EE4 decaf to regular?
Did you check Chrome Dev Tools for an error in the console?
|
|
sylvinic
|
September 16, 2020 at 6:08 pm
Yes I did get it while switching.
I did not check Chrome Dev Tools (I don’t know what that means, but will try to figure it out. Take it easy on me…I’m just a church volunteer trying to set up a curbside turkey dinner!)
Would the Chrome issue be why functions (like creating a ticket, deleting ticket options, and moving the order of the ticket page) aren’t working?
|
|
Tony
|
September 17, 2020 at 1:18 pm
Yes I did get it while switching.
Then, for now, it’s not worthing worrying about.
If you are consistently getting an error we can investigate but it sounds like something was searching for decaf right after you switched to regular.
I did not check Chrome Dev Tools (I don’t know what that means, but will try to figure it out. Take it easy on me…I’m just a church volunteer trying to set up a curbside turkey dinner!)
Would the Chrome issue be why functions (like creating a ticket, deleting ticket options, and moving the order of the ticket page) aren’t working?
Just to clarify, this isn’t a ‘Chrome issue’ but using Chrome you can find the error being thrown and go from there.
However, to answer your question, yes, the issue I was trying to check using Chrome Dev Tools would cause the above. The ‘fix’ for this doesn’t hurt anything if its not the cause so maybe we can just jump to that for now, it will at least get you up and running again for the time being.
On the site go to Dashboard -> Plugins -> Add New.
In the search bar on the top right add ‘enable-jquery-migrate-helper’
Like so: https://monosnap.com/file/2mi2qEh2Ozgu0bdnB63MVSOqT6xj9O
Click install, then activate.
Same issue?
|
|
sylvinic
|
September 20, 2020 at 11:48 am
Yes, that plug-in you suggested provided a warning. And I checked the Chrome Developer tools, at saw errors as well (though they don’t make much sense to me).
I have attached images of each. Are you able to help? Or if I purchased a token, would these be easily solved? I need this up and running asap. All I need to do is add 6 more ticket types.
jQuery Migrate Helper — Warnings encountered
This page generated the following warnings:
https://hamptonnhumc.org/wp-content/plugins/event-espresso-core-reg/core/admin/assets/ee-admin-page.js: jQuery.fn.unload() is deprecated
https://hamptonnhumc.org/wp-content/plugins/event-espresso-core-reg/core/admin/assets/ee-help-tour.js: jQuery.fn.load() is deprecated
Please make sure you are using the latest version of all of your plugins, and your theme. If you are, you may want to ask the developers of the code mentioned in the warnings for an update.
If you need the Chrome errors:
|
|
Tony
|
September 21, 2020 at 10:56 am
Yes, that plug-in you suggested provided a warning. And I checked the Chrome Developer tools, at saw errors as well (though they don’t make much sense to me).
Enabling that plugin didn’t ‘fix’ the problem with the editor then?
The notices you posted above (there’s no Google Chrome console screenshot) won’t cause any errors on EE’s page, we are aware of those notices but they won’t cause the problem you have.
I have attached images of each. Are you able to help? Or if I purchased a token, would these be easily solved? I need this up and running asap. All I need to do is add 6 more ticket types.
The errors posted aren’t the problem so I can’t answer that.
Can you send me login details so I can take a quick look? I can gauge from there if you’ll need a support token or not as it depends how deep I’ll need to go.
To send credentials you can use this form:
https://eventespresso.com/send-login-details/
|
