|
richard sandilands
|
November 29, 2016 at 8:23 pm
All of a sudden our users are not able to checkout — they receive validation errors on the form even if all fields are filled out.
I’ve tested the checkout and can confirm that even though all fields are filled out, the user gets a validation errors for all fields.
Screenshot here: http://i.imgur.com/kvtW6BZ.png
Any clues would be appreciated — this is rather urgent. We’ve have over a dozen orders fail in the last hour.
|
|
richard sandilands
|
November 29, 2016 at 8:35 pm
I can’t be fully certain but it seems this started occurring after updating to Event Espresso 4 Core Regular v4.9.22.p
|
|
richard sandilands
|
November 29, 2016 at 8:54 pm
I notice too that the settings for the User Integration Add-on are doubling up:
http://i.imgur.com/BYZyb43.png
That is, I am seeing two copies of the same settings.
|
|
richard sandilands
|
November 30, 2016 at 1:08 am
There’s also this error showing up in our logs:
2016/11/30 08:03:31 [error] 486#0: *116158 FastCGI sent in stderr: "PHP message: PHP Warning: Invalid argument supplied for foreach() in /www/bookingsbyroncliniccomgc_570/public/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Tabbed_Content.helper.php on line 109" while reading upstream, client: 10x.xx.2xx.xxx, server: www.bookings.byronclinic.com, request: "GET /wp-admin/admin.php?page=espresso_registration_form&action=wp_user_settings&_wpnonce=82ac9c253d&wp_user_settings_nonce=82ac9c253d&return=update_wp_user_settings HTTP/1.0", upstream: "fastcgi://unix:/var/run/php7-fpm-bookingsbyroncliniccomgc.sock:", host: "bookings.byronclinic.com", referrer: "https://bookings.byronclinic.com/wp-admin/admin.php?page=espresso_registration_form&action=wp_user_settings&wp_user_settings_nonce=82ac9c253d"
|
|
richard sandilands
|
November 30, 2016 at 2:00 am
Priority support request submitted. NB site is under EE maintenance mode.
|
|
Josh
|
November 30, 2016 at 7:12 am
Hi Richard,
We are looking into this, however, we’re having some trouble with logging into your website. When we try to visit your site’s login page, it redirects to a home page. Can you please disable that?
|
|
richard sandilands
|
November 30, 2016 at 8:38 am
Hi Josh
I can’t even start to think where that redirection is coming from — certainly nothing I’ve set up.
I’ll have a closer look now.
|
|
richard sandilands
|
November 30, 2016 at 8:58 am
OK, you should have access now at the url provided earlier.
Its’ the middle of the night here and I’d forgotten that we were disabling the backend for a certain period of time via a security plugin.
Thanks, I really hope we can find a solution here.
|
|
richard sandilands
|
November 30, 2016 at 9:07 am
I’ve also disabled the EE maintenance mode for now
|
|
Josh
|
November 30, 2016 at 9:17 am
Hi Richard,
Is there a specific event that I should be testing in order to get the validation errors? The reason I ask is because I started one registration and was able to proceed to the payment page after filling out the registration form, and there were no validation errors.
The other thing that may have happened is when you’re disabling the backend for a certain period of time via a security plugin, that also has the unintended consequence of disabling the ajax in the registration form (which is tied to the backend of the WP website).
|
|
richard sandilands
|
November 30, 2016 at 9:33 am
The validation errors come on the payment page — sorry for the confusion.
|
|
Josh
|
November 30, 2016 at 9:55 am
I’m not seeing any validation errors there either, with the Chrome browser. However, with the Firefox browser, I’m seeing a JavaScript error from the Divi theme, so that could potentially cause some validation issues for some browsers. May I ask which browser are you using?
|
|
richard sandilands
|
November 30, 2016 at 10:07 am
It’s occurring in all browsers. I was just able to replicate the issue in Chrome and Safari.
The last dozen or so “pending payment” orders all failed for the same reason as I had personal contact with each person.
I think the issue is that you nee to fully complete the form with a live credit card to see the error. I’m using a real credit card here to produce the error.
|
|
Josh
|
November 30, 2016 at 10:08 am
Does the error happen if you temporarily switch to another WordPress theme?
|
|
richard sandilands
|
November 30, 2016 at 10:14 am
Yes, also happens in 2016 theme.
See screenshot here http://imgur.com/a/Qc6Ua
|
|
richard sandilands
|
November 30, 2016 at 10:19 am
Had to delete the screenshot as it contained sensitive data.
New one here http://imgur.com/a/BmBLq
|
|
richard sandilands
|
November 30, 2016 at 10:32 am
NB the double up of system questions on the EE Registration Form admin page
https://bookings.byronclinic.com/wp-admin/admin.php?page=espresso_registration_form
I note that there are 2 of the system questions — each of which is required so I am wondering if this is the cause of the validation issue?
|
|
richard sandilands
|
November 30, 2016 at 10:34 am
Although that might be a seperate issue as the validation errors are in relation to the billing details, not the attendee details.
|
|
Josh
|
November 30, 2016 at 10:47 am
Yeah that’s a separate issue. The validation errors that are happening are related to the MIGs gateway setting to “Open by default”. I’ve set that setting to No and that should prevent those validation errors, can you verify? There will need to be a fix made to either EE core or the Migs gateway (or both) to ensure that the proper scripts load when that setting is set to Yes.
|
|
richard sandilands
|
November 30, 2016 at 11:03 am
OK, I was able to get a payment through that time — I did get a white screen after payment processing which upon refreshing led to the proper thank-you page.
I can see the approved order in the backend and confirm that messages were sent.
With the “Open by Default” button off, it’s very hard for users to know to click the radio button to choose the MIGS gateway, our only payment option. SO that presents an issue pending a fix. I’m not sure how I can direct users to click that radio button, everyone will miss it without some instruction, maybe I need to edit the template to allow for this.
No changes were made to our settings prior to this happening yesterday out of the blue — was there an update to the MIGS add on that came out yesterday? I did notice a couple of EE updates, to core (4.9.22.p) and also to an add-on but don’t recall which add on it was.
It’s now 5am here, I’ve been up all night and today was set to be our biggest day for orders for the year for us, with up to 100 orders per day over the the next 2 days expected due to our ‘early bird’ cut-off tomorrow and following an email blast to our list yesterday. I’m going to be lucky if I still have a job when I go into work in a few hours.
So the timing for this is incredibly stressful.
|
|
richard sandilands
|
November 30, 2016 at 11:21 am
Would rolling back to 4.9.21.p be helpful here?
|
|
Josh
|
November 30, 2016 at 1:20 pm
No because the part of this that needs fixing is the MIGs gateway. One of the developers that works with the payment gateways found a setting in the MIGs that was not correct, and it’s a one line fix. I’ve applied the fix to your website, and set the Open By Default option back to Yes. So when you take EE out of Maintenance mode, the MIGs gateway billing form will work as expected.
|
|
richard sandilands
|
November 30, 2016 at 1:26 pm
Oh that’s great news! You’ve made my day, thanks.
|
|
richard sandilands
|
November 30, 2016 at 1:38 pm
I just ran another order through successfully using our credit card.
Still white screening on the thank-you page though — is this something you are able to look at? It’s weird as it loads in Firefox but not in Safari.
The thank you page for the completed order is this:
https://bookings.byronclinic.com/thank-you/?e_reg_url_link=1-7cb2a98ef98222dde451684a47e283d6
|
|
Josh
|
November 30, 2016 at 1:39 pm
No problem. There are a few housekeeping items from the plugins page on your site that I noticed that can/should be addressed at some point (not urgent at the moment) :
1) The States/Countries pack plugins can be removed. Those actually add the states/country data to the database when they are activated. Once that’s data is recorded to the database, those plugins should be deactivated then deleted from the site. They should not be left activated.
2) The version of the MIGs gateway on your site is an older release candidate version. Now that your copy has been patched, it’s fine for now, but going forward in order to get update notifications you’ll need to install a final release version. So when EE4 MiGS Payment Gateway version v1.0.3.p is released, you’ll need to remove the MiGS gateway release candidate from your website and replace it with version 1.0.3.p. I’ll update this thread when version 1.0.3.p is released.
|
|
richard sandilands
|
November 30, 2016 at 1:46 pm
Thanks Josh, orders are coming in again now.
I’m just putting this up here now too:
http://pastebin.com/2CFhJpBy
The error logs are showing variations on that error ^
|
|
Josh
|
November 30, 2016 at 2:11 pm
We can look into those errors, and you should probably remove that paste bin since it has sensitive server info included in the directory paths.
|
|
richard sandilands
|
December 1, 2016 at 1:22 am
Thanks for your help Josh, we had a very smooth day today with lots of orders and no hiccups.
|
