|
Armen Orujyan
|
March 2, 2015 at 8:51 am
Hi,
We are already life and one of our registrants have gotten this error: “This registration step could not be completed. Please refresh and try again”.
We had people register successfully, but at this point, we don’t know how many have gotten this error and just gave up. I have tested it and cannot recreate it – it goes through.
1) Is there a way to fix it
2) Is there a way to trace people’s attempts to register / error log or something of that nature.
This is a second issue happening with the registration process (first one was related to the caching enabled and we have resolved that already) and without some kind of tracking process at the very least, it is really unreliable.
|
|
Tony
|
March 2, 2015 at 9:12 am
Hi Armen,
“This registration step could not be completed. Please refresh and try again”.
There are lots of reasons for this error, I ran a registration and didn’t run into any issue like yourself, I will run a few registrations to see if I can reproduce. However I did notice your Event Espresso pages are still served from W3 Total Cache – http://take.ms/TehpB
How did you resolve the previous issue with caching?
|
|
Armen Orujyan
|
March 2, 2015 at 9:18 am
We have followed your instructions from one of the posts by someone else and have put EE critical pages on the non-cache list. It had worked at the time.
|
|
Tony
|
March 2, 2015 at 9:43 am
Your site currently has Permalinks set to the default, like this – http://take.ms/1b2vG
That is within Settings -> Permalinks.
Is that a recent change? Did the site previously use ‘post name’ permlanks?
|
|
Armen Orujyan
|
March 2, 2015 at 9:52 am
Default from the start – no changes
|
|
Tony
|
March 2, 2015 at 10:14 am
Does your server support ‘pretty’ permalinks such as ‘Post Type’?
This guide posted here:
https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/
Checks your URL for the Event Espresso critical page names, with default permalinks they are never within the URL. For example here is a default permalink:
http://www.domain.com/?p=1234
W3 Total Cache checks that URL and does not see any of the strings we added in to exclusion list.
With ‘pretty’ permalinks, the same page could be:
http://www.domain.com/events/
W3 Total Cache checks that URL for ‘/events/’ and then knows not to cache it.
It likely worked previously when you set it up as you cleared the cache when doing so, also logged in users are not served cache pages.
|
|
Armen Orujyan
|
March 2, 2015 at 10:38 am
we currently cannot change permalinks because our social media counts disappear when doing so and no work-arounds have worked so far.
is there any other way to solve it but change permalinks to “pretty”?
|
|
Tony
|
March 2, 2015 at 11:37 am
we currently cannot change permalinks because our social media counts disappear when doing so and no work-arounds have worked so far.
Are these counts from another plugin?
I currently can not reproduce the error, until I can see the error I’m not sure if this will resolve the issue, however Event Espresso pages being cached will cause problems with your registrations at some point and could very
You could add the page id’s of the EE pages to the the do not cache list.
Go to Event Espresso -> General Settings -> Critical Pages.
You will see a list of 4 pages – http://take.ms/UW60O
Edit each of those page, look at the permalink under the event title and make a note of the page_id, for example for my Espresso Checkout page on this site it is 4 – http://take.ms/lere5
So I would add page_id=4 to the do not cache list, like this – http://take.ms/YzawS
(The ID numbers for your site will be different)
However this would work much better if ‘pretty’ permalinks where enabled.
|
|
Armen Orujyan
|
March 3, 2015 at 9:30 am
Hi Tony,
I have enabled the “pretty” links, updated the non-cache pages to include EE critical pages. The problem persists, today we learned more people had an issue with the process.
I understand there might be many reasons, but that renders the plugin unusable because we are absolutely blind to how many people encountered the problem, where it lies, how to solve it, and how many of those problems there are.
Is there any practical solution to this?
|
|
Lorenzo Orlando Caum
|
March 3, 2015 at 9:55 am
Hi Armen, could you deactivate the caching feature in your caching plugin and deactivate your caching plugin.
Note: there are two steps, otherwise the old cache may still remain
Then launch an alternative web browser (i.e. use Firefox if you are using Internet Explorer) and re-test.
If it begins to work, then I would try WP Super Cache instead.
—
Lorenzo
|
|
Armen Orujyan
|
March 3, 2015 at 3:08 pm
Hi Lorenzo,
I have been able to re-create the issue with different scenarios:
1. [before disabling the cache plugin] internet connection lost and re-established; the page is refreshed with the info filled out. “clicking proceed to payment” gives this: “An error has occurred:
Your form data could not be applied to any valid registrations.
EE_SPCO_Reg_Step_Attendee_Information – process_reg_step – 593”
2. [before disabling the cache plugin] filled out the form, clicked “proceed to payment”, then clicked back button, a form filled loaded, clicked “proceed to payment” – same result
3. [after disabling the plugin in two steps] same as scenario #2 – result: something along the lines of “you cannot proceed because you have not selected payment options, please refresh and try again”; refreshing and filling it out again (loaded empty) results in the same mistake
4. [after activating the WP Super Cache] same as #3 but the error message is “An error has occurred:
Your form data could not be applied to any valid registrations.
EE_SPCO_Reg_Step_Attendee_Information – process_reg_step – 593”
Now these are specific examples however out of 10-12 registrations only one registration were able to register without me processing it manually. 5 have contacted me directly to report the issue, the rest are just pending so i am not yet certain of the reasons – will go back to ask them to comment. the reason i bring it up is I don’t think all of them have pressed back button or lost connection, there must be more scenarios.
|
|
Lorenzo Orlando Caum
|
March 3, 2015 at 3:56 pm
Alright Armen, thanks for the additional testing.
We had a member earlier today that had registration issues and it was due to old caching files that did not clear even though the caching plugin was deactivated in the WordPress Plugins screen.
Another issue is that the caching plugins usually cache differently for logged-in users vs. public visitors so you could have a registration that works while a public visitor has one that fails.
Try these steps to ensure any old caching files are gone.
1) Clear the cache, turn off the caching feature, and deactivate the caching plugin. For example, if you are using WP Super Cache, then make those changes through that plugin
2) Login to your WordPress site with an SFTP or FTP client and browse to location:
/wp-content
Then delete any cache_ related files that you may see there
3) Login to your WordPress dashboard and go to the Plugins screen and update Event Espresso 4:
https://eventespresso.com/wiki/ee4-changelog/
4) Then browse to WP-admin –> Settings –> Permalinks. This simply refreshes permalinks. No actual changes on the page are needed.
From here, launch an alternative web browser and then try a registration. Do any errors occur on your end?
If not, could you then test in a different web browser?
Let us know what you find.
Thanks
—
Lorenzo
|
|
Armen Orujyan
|
March 3, 2015 at 7:16 pm
it seems it has worked Lorenzo, thank you. do i install the plugin back? we got it only due to the very first time people had trouble registering.
|
|
Lorenzo Orlando Caum
|
March 4, 2015 at 1:36 pm
Great Armen. The old caching may have been the cause as I’ve seen it happen a few times, though I’m not sure why it happens.
Here are the steps to reactivate your caching plugin. In this case, I would use WP Super Cache.
1) Reactivate your caching plugin through your WP-admin (WP dashboard)
2) Enable the caching feature
3) Setup the no-cache rules through the advanced features area of WP Super Cache:
https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/#wpsupercache
Be sure to save changes on the page after adding those page slugs.
Then clear your cache via your caching plugin.
Thanks
—
Lorenzo
|
