|
SJCP Webmaster
|
October 24, 2015 at 11:00 am
We’ve been getting reports of users not able to get through to the payment options page. There have been two scenarios that have been reported. The first is that they receive the message “An error has occurred: Your form data could not be applied to any valid registrations.” The second is that the user does not receive a message at all and instead the spinning cog continues to spin indefinitely.
I have reproduced both scenarios, however, the issues appear to happen very intermittently. I have only been able to reproduce them when I throttle my internet connection. We recently updated the EE plugin. Since then, I have only been able to see the spinning cog issue. However, since they are difficult to reproduce, I’m not sure if that is just because I haven’t tested enough.
In our last event, quite a few people emailed us about registration issues. And we are unsure how many people have been turned away because of any registration problems. We are starting to push registration for our next event in the winter and naturally are looking to resolved these issues.
With the spinning cog issue, I noticed that the site sends out two requests to https://www.saintjohnscamp.org/wp-admin/admin-ajax.php . When registration works, the second request has the element “return data” with a bunch of info as well as the “payment amount” is something other than 0. When registration fails, “return data” is not existent and “payment amount” is 0. Here is the second response: {“success”:null,”registration_time_limit”:”01:00:01″,”payment_amount”:0}
|
|
Tony
|
October 26, 2015 at 7:46 am
Hi Luke,
Do you have access to the servers error logs?
If so can you take a look within those and see if there are any EE related errors being thrown please.
You could enable error logging within WordPress using:
define( 'WP_DEBUG', true ); // Or false
if ( WP_DEBUG ) {
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
}
Which will store the errors within /wp-content/debug.log
There are lots of reasons for both of those errors to be thrown, so we need to narrow this down some and grab the error that is thrown.
If you enable WP_DEBUG on the site and let us know when, we can run some test registrations and see if any errors come up.
|
|
SJCP Webmaster
|
November 5, 2015 at 8:27 pm
Sorry for the delayed response. Debugging was not set up before so I went ahead and enabled it.
|
|
SJCP Webmaster
|
November 5, 2015 at 9:33 pm
I do have access to some error logs. The last errors from EE was from July. Since we have been having issues after that, I figured they probably aren’t relevant at this point.
|
|
SJCP Webmaster
|
November 5, 2015 at 9:41 pm
I was able to reproduce the spinning cog issue at 11:38 EST.
|
|
Tony
|
November 6, 2015 at 4:01 am
Sorry for the delayed response. Debugging was not set up before so I went ahead and enabled it.
Did you use the code I posted above in your wp-config.php file?
I do have access to some error logs. The last errors from EE was from July. Since we have been having issues after that, I figured they probably aren’t relevant at this point.
Errors from that far back are likely unrelated to this.
I was able to reproduce the spinning cog issue at 11:38 EST.
If you check the error logs and look around that time are there any EE errors? If you used the code I posted above you will find a debug.log file within /wp-content/ that will have stored any errors thrown.
|
|
SJCP Webmaster
|
November 6, 2015 at 3:17 pm
Yes, I used the code you posted.
I did not see any new errors from when I ran that test. I do see these errors constantly:
I did not see any errors in the other error logs either that pertain to that day
|
|
Lorenzo Orlando Caum
|
November 8, 2015 at 10:44 am
Hi Luke,
It sounds like this issue is happening sporadically. It could be that the site is hitting a memory limit and so it stalls out.
Could you add the following macro towards the middle of your wp-config.php to raise the memory that is available to PHP?
define( ‘WP_MEMORY_LIMIT’, ‘128M’ );
https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP
—
Lorenzo
|
