Update to 3.1.8 errors

  • Resolved adamspider

    (@adamspider)


    4 years, 7 months ago

    This morning I updated to v. 3.1.8 and immediately started seeing issues. The most important one was that the Stripe credit card fields were no longer visible on the checkout page. There were also two errors at the top of the page:

    Warning: array_merge(): Expected parameter 2 to be an array, null given in /nas/content/staging/crossclave/wp-content/plugins/woo-stripe-payment/includes/class-wc-stripe-frontend-scripts.php on line 74

    Warning: array_walk() expects parameter 1 to be array, null given in /nas/content/staging/crossclave/wp-content/plugins/woo-stripe-payment/includes/class-wc-stripe-frontend-scripts.php on line 77

    I reverted to 3.1.7 and the issue resolved, but I wanted to report here. (I’ve got a video of the before and after as well if that’s helpful.)

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Payment Plugins

    (@mrclayton)

    Hi @adamspider

    Thanks for contacting us and reporting this issue.

    On your site do you only sell digital products or do you have products that require shipping?

    Kind regards,

    Thread Starter adamspider

    (@adamspider)

    Only digital products. No shipping at all. (And thanks for your very quick response!)

    Plugin Author Payment Plugins

    (@mrclayton)

    @adamspider

    OK cool thanks for confirming. I’ll run some tests and see if I can re-create the issue. I think it may have something to do with woocommerce not returning an array of shipping fields.

    Are you aware of any filters that you are hooking into to return an empty set of shipping fields?

    Thread Starter adamspider

    (@adamspider)

    Yes, we disable the address fields and shipping fields to streamline the checkout process. The plugin we use for this is called Checkout Manager – https://quadlayers.com/portfolio/woocommerce-checkout-manager/

    Plugin Author Payment Plugins

    (@mrclayton)

    @adamspider

    Thanks for that info, it’s very helpful. That’s what’s causing that message. The Stripe plugin is expecting an array of checkout fields but null is being returned by the checkout manager plugin.

    I will do some testing on my end, but it looks like I’ll have to create a validation to ensure null is not returend.

    Kind Regards,

    Thread Starter adamspider

    (@adamspider)

    Thanks again for the quick responses. If you need help testing please let me know. Happy to help in any way I can.

    Plugin Author Payment Plugins

    (@mrclayton)

    Hi @adamspider,

    Thanks for the offer to help test. Please reach out to me via the Help button located on all the Stripe plugin settings pages. I can send you a copy to test before I release a patch.

    Kind Regards,

    Plugin Author Payment Plugins

    (@mrclayton)

    @adamspider,

    I just released a patch to 3.1.8. Can you deactivate, delete, then re-install version 3.1.8 from the Admin Plugins page of your site and then test? It should be all good now.

    Kind Regards,

    Thread Starter adamspider

    (@adamspider)

    Success! I tried this in my staging environment and it looks to be working as it should. Thanks so much for your quick response

    Plugin Author Payment Plugins

    (@mrclayton)

    @adamspider sweet thanks for confirming and bringing that to our attention.

    Almost 99% of merchants will not modify those checkout fields but I’m glad you pointed out this edge case so we could account for it.

    Kind regards,

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Update to 3.1.8 errors’ is closed to new replies.