|
Studio Chevalking
|
May 25, 2018 at 1:54 am
After they fill in the form people get the message that something went wrong.
In the log file I see this error: EE_SPCO_Reg_Step_Attendee_Information proces-s_reg_step – 841
On an normal browser on the computer it works fine, it is only a problem when people use a mobile phone. On the iPad there is also no problem.
Is there an solution for this?
Greets Wilfred
|
|
Tony
|
May 25, 2018 at 4:45 am
Hi there,
I just ran 2 registrations on one of your events, 1 on pc and another on a Samsung S8 without any problems.
Is this happening on a specific event? If so can you link me to that event, please?
|
|
Studio Chevalking
|
May 25, 2018 at 5:27 am
Aah tnx for the test! I did see the registration… Strange because I always see this error and receive also from participants the message that it won’t work on de telephone.
Maybe it’s an iPhone problem?
It is on all the events by the way.
|
|
Studio Chevalking
|
May 25, 2018 at 5:27 am
Until now I Did not ask to people which telephone they use, I will ask for it!
|
|
Josh
|
May 25, 2018 at 9:18 am
What you can do to troubleshoot this further is you can rule out a plugin or theme conflict. First, you install the Health Check plugin.
Then you log into your site with your iPhone. (log in with the administrator’s account)
Then you go to WP → Dashboard → Heath Check → Troubleshooting. There you’ll Enable Troubleshooting Mode, then once that’s activated you’ll reactivate Event Espresso only via the Health Check’s Troubleshooting > Plugins item in the WP admin bar.
At that point, only the Event Espresso plugin will be activated while testing the site with the iPhone and you can check to see if the issue persists.
|
|
Studio Chevalking
|
May 25, 2018 at 2:21 pm
Hi, I did the testing and the issue remains.
🙁
|
|
Josh
|
May 25, 2018 at 3:54 pm
May I ask can you check to see if you get any errors if you use your phone to register for an event on this demo site:
https://demoee.org/barnwoodworkshop/events/wood-stone/
|
|
Studio Chevalking
|
May 26, 2018 at 1:39 am
I did, it worked fine!!
|
|
Josh
|
May 26, 2018 at 10:57 am
It seems we’ve narrowed things down to the server, because you’ve ruled out plugin conflicts, and your iOS device can register for and event on another site that has Event Espresso. Can you check with your host to see if there’s anything set up that would affect requests from an iOS device? Maybe there’s a firewall or some mod_security rules related to the error you’re seeing.
|
|
Studio Chevalking
|
May 27, 2018 at 4:39 am
I see one error in the health check, this also appears when I check on the computer:
The loopback request to your site failed, this may prevent WP_Cron from working, along with theme and plugin editors.<br>Error encountered: (0) cURL error 28: Operation timed out after 10000 milliseconds with 0 bytes received
Besides this there is also one attention which isn’t an error (also this one appears as well on the computer and mobile):
Your version of cURL, 7.54.0, is slightly out of date. The most recent version is 7.58. This may in some cases affect your sites ability to communicate with other services. If you are experiencing connectivity issues connecting to various services, please contact your host.
The cron job could be a thing! But strange that the error is on both, but the problem only on mobile.
…hope that it will help!
|
|
Josh
|
May 29, 2018 at 6:53 am
Those do not sound like they’d cause the issues you’re seeing on the mobile device. Can you check with your host to see if there’s anything set up that would affect requests from an iOS device?
|
|
Studio Chevalking
|
June 5, 2018 at 7:33 am
I’ve disabled different espresso plugins, but it still won’t work…
Even on an iPad some had trouble… That was new to me…
I have no clue wat to do.
|
|
Studio Chevalking
|
June 5, 2018 at 7:58 am
This is the error which occurs: EE_SPCO_Reg_Step_Attendee_Information proces-s_reg_step – 841
|
|
Studio Chevalking
|
June 5, 2018 at 8:29 am
In an scan there where several errors with Event Espresso:
Fatal error: Uncaught InvalidArgumentException: The namespace for this manifest file has already been registered, choose a namespace other than event-espresso-core-regespressophp in /home3/wilfred/public_html/sc/wp-content/plugins/event-espresso-core-reg/core/services/assets/Registry.php:463
Stack trace:
#0 /home3/wilfred/public_html/sc/wp-content/plugins/event-espresso-core-reg/core/services/assets/Registry.php(444): EventEspresso\core\services\assets\Registry->registerManifestFile(‘event-espresso-…’, ‘https://www.stu…’, ‘/home3/wilfred/…’)
#1 /home3/wilfred/public_html/sc/wp-content/plugins/child-theme-configurator/includes/classes/Preview.php(121): EventEspresso\core\services\assets\Registry->registerManifestFiles(0)
#2 /home3/wilfred/public_html/sc/wp-includes/plugin.php(453): WP_Hook->do_a in /home3/wilfred/public_html/sc/wp-content/plugins/event-espresso-core-reg/core/services/assets/Registry.php on line 463
|
|
Josh
|
June 5, 2018 at 9:52 am
That’s actually an error from the Child Theme Configurator admin page and shouldn’t affect anything happening on the front end.
|
|
Studio Chevalking
|
June 6, 2018 at 3:14 am
I see…
I’ve turned on the debug log and I get this:
[06-Jun-2018 09:11:37 UTC] add_to_cart_fragments is deprecated since version 3.0.0! Use woocommerce_add_to_cart_fragments instead.
[06-Jun-2018 09:11:37 UTC] The WC_Cart::get_cart_url function is deprecated since version 2.5. Replace with wc_get_cart_url.
|
|
Tony
|
June 6, 2018 at 3:49 am
Those notices aren’t from Event Espresso as it does not integrate with Woocommerce, they will be from either your sites theme or another plugin (I see you have a few specifically for woo so I’d start with checking those).
I just tested another registration using an iPad and again didn’t run into any problems (I intentionally took longer to enter my details than previous registrations).
You mentioned earlier your iPad was working fine on your site, so may I ask how you were testing EE with the health check plugin if your iOS device could register anyway?
Are you using another device to reliably trigger the error? If so what device?
|
