Posted: September 14, 2016 at 8:20 pm
|
After registering for an event and the payment being processing via Stripe, our thank you page is displaying the message below. The full URL with query string is present and the shortcode is verified in the critical pages settings. This has recently started happening after we moved the site to a new server and started using HTTPS. Please advise how we can resolve this issue. We’re sorry… We are running EE 4.9.12.p and WordPress 4.6.1. Theme is Avada. |
Hi there, When you set up the site with https, did you use the Really Simple SSL plugin, which is the recommended plugin from the first part of our https guide? |
|
|
We did not, but I have since activated that plug-in, retested, and I’m still having the issue. What else should we look at? |
September 15, 2016 at 10:03 am There are a few other possible causes to this issue. You can rule these out one by one: |
|
|
September 15, 2016 at 11:45 am Ruled out #1 and #2. Turn on debug mode and we’re seeing these errors on the Thank You page: The following errors have occurred: Please advise. |
When you moved to a new server, was the database properly migrated, especially the options table? There may be an issue with the option for the Thank You page, which may be corrected by going to Event Espresso > General Settings, and re-saving the Critical Pages settings, and double checking the Thank You page content for the thank you page short code, and updating that page. |
|
|
Unfortunately, that didn’t seem to help. We’re also seeing the error below our event details pages (https://canadianlasersafety.com/events/aesthetics-laser-safety-officer-training-10/). Perhaps this issue is contributing to the Thank You page issue page issue as you move from this page through to registration and checkout. WARNING: wp-content/plugins/event-espresso-core-reg/shortcodes/espresso_ticket_selector/EES_Espresso_Ticket_Selector.shortcode.php:64 – extract() expects parameter 1 to be array, string given |
|
Please disregard my last note, I have resolved that issue, and it’s not linked with the Thank You page issue. We are at a loss now, how else can we troubleshoot? |
When you moved to a new server, was the database properly migrated, especially the options table? For example, was it simply copied over, or were the serialized strings converted to point to the new server’s file paths? |
|
|
Yes, the database was properly migrated. Unless you have something else for us to try can we give you the means to have a closer look at how the site is built? |
Do you have object caching or any other type of caching set up on the new server? |
|
|
No, only media (images, video) caching. |
|
Here is a list of the active plug-ins on our site for troubleshooting purposes: Akismet |
The plugins are not the concern at this point. Remember that you deactivated all of those and it was still broken? Can you verify with the host that there’s not any built in caching mechanisms in place, like object caching or varnish? If the only thing that’s changed since things started breaking was you moved to another host, that’s a good indication it’s something happening at the server’s configuration level. Which also means that logging into the WP dashboard isn’t going to help much for troubleshooting. |
|
|
I have verified with the host that there are no caching mechanisms in place on the server. |
Can you check to see if sessions can be written to a temp folder? The other thing you could try is deactivate Event Espresso, then delete the Thank You page, not just put it in the Trash, but Trash it, then delete it. Then you reactivate EE4, and navigate to Event Espresso > General Settings > Critical pages to verify that a new Thank You page has been created. If it’s not caching, then something in the config might have got messed up when the data was moved from the original server. |
|
|
September 16, 2016 at 11:38 am Unfortunately, we cannot have sessions written to a temp folder. We followed your direction to delete the Thank You page and reactivate EE to create a new Thank YOu page. The page is in the list of critical pages and the page status and shortcode are Ok. |
|
September 16, 2016 at 11:53 am Sorry forgot to mention that we retested and are still receiving the error message. |
Why not? If your server isn’t allowed to write PHP sessions, then you’ll need to move to a server that meets that requirement in order to use Event Espresso. Event Espresso uses sessions as a way to identify each transaction. |
|
|
We are writing sessions to the /var/lib/php/session folder. We are also wondering if improper ticket setup in our event could cause the error message? |
What would constitute an improper ticket setup? Was the ticket setup the same way when it was on the other server, where things were working. It sounds like something got borked when the site was moved from server A to server B, but so far in the back and forth here, very little information has been given about how the site was moved from the original server to the other. The key to resolving this issue may be finding what’s different about this new server, or what didn’t get migrated correctly. |
|
|
Tickets were not changed from when the site was on the old server to the new server. Regarding the migration – the only thing that changed was going from an http site with no SSL certificate to a site with https and an SSL certificate. Also note that we have only saw the correct Thank You page when we were in test mode with Stripe. After we moved to the current https server we started testing Strip in production mode and are where we are now with a non-functional Thank You page. Is there a way to setup no-cache/exclusion rules for critical pages? Via WordPress our our host? |
It depends on how caching is set up. We have a number of guides that show how to set up no-cache/exclusion rules: https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/ and how to disable object caching site wide: https://eventespresso.com/topic/incompatible-with-godaddy-managed-wordpress-hosting/ |
|
|
We are not using any of the caching plugins and our host does not have an internal caching system. Would adding: define(‘WP_CACHE’, ‘false’); to wp-config do the trick? |
If you’re not using caching plugins and your host does not have an internal caching system, why are you asking about how to disable caching? |
|
|
I guess that wouldn’t make sense, please disregard. At this point it looks like we may have to start fresh with Event Espresso. What would you recommend? Create new events isn’t a problem, however I would want to avoid re-coding the HTML messages we’re sending because they were time consuming to configure. |
|
If it helps, you could have a look at our site on our staging server (no https) at cls.keyrise.com. Stripe is in test mode on this server but test transactions are returning the Thank You page without any errors. |
This issue was resolved through a support token but noting the result here. The problem was due to OpCache being in use on the server, disabling that allowed the pages to function as expected. |
|
The support post ‘Thank You Page Returning We're Sorry Message’ 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.