Posted: June 11, 2015 at 12:10 pm
|
Hello I just today updated to the latest version of EE and EE stripe gateway. I went on to create a new event. I use the ticket selector shortcode on custom created pages and the ticket selector appears fine. However, whenever somebody attempts to register any of the tickets the following message appears. This does not seem to happen with my other event I created before the update. Please assist. Thanks, Kyle —— WordPress Version: |
Hi Kyle, It looks like you forgot to include a link to where we can test a registration. Can you reply back with a link? Also, can you check with your host to see if they have any server level caching or varnish active on this site? |
|
|
I’m looking into the server side issues currently. You can try a registration at Thanks! |
|
I checked with my host and there is no server level caching or varnish active. |
Hi Kyle, I have a few questions about the way this event page is set up vs. the other event. Does the other event have its own page? Do you know why there isn’t a ticket selector displaying on /events/forth-queerly/, but there is a ticket selector on /events/west-coast-communities-conference/? |
|
|
I have always set up events to have their own page that I custom create for a number of formatting reasons, so the other event does have its own page. I have no idea why the ticket selector is displaying for one versus the other on the /events/ pages. I checked previous /events/ pages and none of them have ticket selectors either, though this may be because the events are past? Thanks for your prompt help on this. |
Yes, a past event will not include a ticket selector. One interesting thing I’ve found is the event in question does allow registration if I try it with the Firefox browser, but not with Chrome. This may suggest an issue with JavaScript. Can you check to see if anything changes if you remove the social share buttons from the page? |
|
|
I removed the social sharing buttons and nothing changed. Also, I tried to register from my iMac on Firefox and got the same error message. Weird. |
Hi Kyle, Have you or someone involved with building the website made changes to the ticket selector template? The reason I ask is because some of the ticket selector HTML is very different than what the current version of Event Espresso is programmed to output. I can advise looking for a function in the theme or in a customization plugin that’s making use of the |
|
|
I am the only one who has administrative access to the website and I have never changed any code relating to Event Espresso, so that is very strange…. Is there a way to delete and reinstall without losing all my data? Could that even possibly help? |
There’s a slight chance it would help to re-install the plugin. When you re-install the plugin files, you’re not touching the data because the data is stored in a separate location on your web server (the database). You can re-install the plugin files by following this guide: https://eventespresso.com/wiki/updating-event-espresso/#update_manually You can also rule out any theme or plugin conflicts by temporarily deactivating the other WP plugins and switch the theme to 2015 for the admin only with the theme test drive plugin. |
|
|
Wow, so after that whole run-around to find out what was going wrong it turns out it is Event Espresso’s own Stripe gateway add-on that is breaking the main Event Espresso plugin. I’m rather disappointed at this. Something happens when the Stripe gateway add-on is activated which changes the way the /events/ pages display as well as causes the registration to break. This change seems to stay even after deactivating the Stripe plug-in; it is only by deactivating and then activating the main EE plug-in again that the breaks caused by the Stipe add-on go away. Please let me know how this can be fixed ASAP as we currently rely on Stripe for our payment processing. |
|
My apologies, I just tried running just EE and the stripe plug-in and those two alone seem to work fine. The problem is instead in a calendar plug-in called EventON – it seems to interfere with EE probably by using too similarly named functions and data, it just takes a couple minutes for the problem to surface after the EventON plugin is activated. Is there a way to modify either plug-in to eliminate this conflict? |
Hi Kyle, Its likely EventON and EE are using similar URL structures which are conflicting. Can you send me a copy of EventON to investigate? If so please send a copy to support[at]eventespresso.com *Note that whilst we will investigate plugin conflicts it depends on what the cause is as to how much we can do to ‘fix’ the issue within Event Espresso. |
|
Hi Kyle, Both Event Espresso and EventOn use the /events/ slug. I think EventOn is looking for an ‘event’, hooking into the event to add whichever information it is expected to add. This wouldn’t normally be a problem for an EventOn event, but it seems to be hooking into EE events and doing the same. You mentioned you are using a custom page, with EventOn the dashboard includes this menu – http://take.ms/bCK0e So are you creating your custom event page within that section? If so your using EventOn events, to display Event Espresso events, which already sound complicated without any of the extra info Event Espresso uses, without even considering EventOn. You could try changing the events slug for EventOn, within myEventOn -> Settings -> Events Paging -> EventOn Event Post Slug – http://take.ms/leT2d Change that to something like EventOns for example (just something other than EE to test) then view your events. However that will not solve the EE Event within EventOn Events issue mentioned above, but lets start from the beginning and work back. Where do you create your custom events pages? (What section of the dashboard) Which shortcodes are you using to display the event? Are you using EE shortcodes and EventOn shortcodes within the same pages? |
|
|
It appears that changing the event post slug has resolved the issues I was experiencing. Fantastic. Thank you for all your help. |
The support post ‘Registration checkout not working after latest update’ 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.