|
ptsaee4
|
July 7, 2017 at 10:12 am
Hi guys,
Our client purchased your plugin EE4 and their users are having issues registering for courses. They seem to have everything set up correctly and I can go through the process without an issue, but their users are stating that they receive the “This registration step could not be completed. Please refresh the page and try again” error, over and over again.
We’ve purchased a priority support token so I’ll be adding to that shortly.
Cheers,
Chad
|
|
Josh
|
July 7, 2017 at 11:00 am
Hi Chad,
We received your priority support request, but I’m afraid the password you sent for the WordPress account is invalid. Can you verify the correct password and resend the priority support form and include the correct password? Thank you.
|
|
ptsaee4
|
July 7, 2017 at 12:35 pm
Thanks Josh, just re-sent! 😀
Cheers,
C.
|
|
Josh
|
July 7, 2017 at 12:54 pm
Hi Chad,
Before you changed the FTP password and then sent us an invalid password for FTP I was able to get in and bump up the memory limit for how much memory WordPress can access. This may help. I can’t say for sure though because the new password you sent (for FTP is invalid).
Can you reach out to one of the users to see if they still see the error?
|
|
ptsaee4
|
July 7, 2017 at 2:33 pm
Hi Josh,
Yes they are still receiving the error – The last batch of passwords should work (same FTP+Wp-Admin) But I can reset them again if needed!
Thanks!
|
|
Josh
|
July 7, 2017 at 2:51 pm
The WP admin password works fine, no need to reset that one. The FTP password is invalid, can you resend the form and include a valid FTP password? Thank you.
|
|
ptsaee4
|
July 7, 2017 at 2:54 pm
All set!
|
|
Josh
|
July 7, 2017 at 3:00 pm
Can you ask the user(s) to visit this page and send the details to you?
http://supportdetails.com/
|
|
Josh
|
July 7, 2017 at 3:40 pm
Hi Chad,
I’ve deactivated the object caching on your site. That may make the difference for your users.
|
|
ptsaee4
|
July 7, 2017 at 4:07 pm
Hi Josh, we just had a user try with this:
Operating System Windows Windows 7
Screen Resolution 1920 x 1080
Web Browser Internet Explorer 11.0
Browser Size 1754 x 914
IP Address 198.161.9.98
Color Depth 24
Javascript Yes
Flash Version 25.0.-1
Cookies Yes
User Agent
Mozilla/5.0 (Windows NT 6.1; WOW64;
Trident/7.0; rv:11.0) like Gecko
—-
No go 🙁
It’s quite strange because I can’t replicate the issue. I can see the ajax requests are completing successfully with the network inspector.
|
|
Josh
|
July 7, 2017 at 4:23 pm
Hi Chad,
You mention you can’t replicate the issue. Do you know exactly at which point they’re seeing the error? Has anything been changed on the site since the time the last successful registration was completed?
|
|
ptsaee4
|
July 10, 2017 at 8:24 am
Hi Josh, our client responded with:
The issue is happening at step 3:Payment Options. Once the submit is clicked the error message appears.
Those that have been successful had to refresh many times and some have eventually been able to get it to work after multiple tries.
There were some media uploads and post updates this afternoon but there hasn’t been anything significant changed on the website. I just tried again and was successful.
I don’t know if it’s coincidence but it has only been people with manager/administrator access that have been able to register without incident.
—-
I’m going to make a “normal” user account and try to replicate it.
Thanks again for your help!
|
|
Josh
|
July 10, 2017 at 8:35 am
Yeah I haven’t been able to replicate the issue either, and I did tests while logged out of the website. I did disable the caching and set the WP_MEMORY_LIMIT value to a higher limit (which may help if there was an out of memory error). I also activated WP_DEBUG and set it to log only for a while, but I didn’t see any errors that would relate to the payment options step.
I also set the Encode Session Data? option to Yes (in Event Espresso > General Settings > Admin Options, which can help in cases where the session data was getting corrupted.
|
|
ptsaee4
|
July 10, 2017 at 11:09 am
Hi Josh,
I can replicate the issue with a “normal” user with the events that have “Force login” on. Seems like it’s trying to redirect to the /my-account page and triggering that error.
|
|
Josh
|
July 10, 2017 at 12:02 pm
Hi Chad,
You know what’s probably doing that? The custom code in your “PTSA” site-specific functionality plugin. You can remove this part:
add_action ('init' , 'prevent_profile_access');
function prevent_profile_access(){
if (current_user_can('manage_options')) return '';
if (is_user_logged_in()){
if (strpos ($_SERVER ['REQUEST_URI'] , 'wp-admin/' )){
wp_redirect (home_url()."/my-account/");
}
}
}
There may be other functions in that plugin that are interfering as well, which you can rule out by temporarily deactivating that plugin.
|
|
ptsaee4
|
July 10, 2017 at 12:39 pm
Hi Josh,
I commented it out and I think we’re good! Guess that ajax return was messing with the expected response in your guy’s code. Thanks for tracking that down, our old developer was working on this site so I wasn’t aware of those functions 🙂
We really appreciate your help here – thanks again!
Cheers,
C.
|
|
Josh
|
July 10, 2017 at 12:44 pm
It looks like the conditional was a bit too lenient because this:
if (strpos ($_SERVER ['REQUEST_URI'] , 'wp-admin/' ))
would return true with any request to wp-admin, right?
|
