Undefined property

  • Resolved alx359

    (@alx359)


    5 months, 3 weeks ago

    With the last version (4.1.4), getting the debug.log steadily filled with these:

    PHP Warning: Undefined property: WooCommerce::$checkout in \plugins\fluid-checkout\inc\checkout-steps.php on line 269
    PHP Warning: Undefined property: WooCommerce::$checkout in \plugins\fluid-checkout\inc\checkout-steps.php on line 270

    It seems to happen everywhere in the site during page load. Something like this seems to help:

    public function checkout_form_hooks() {
        if ( !is_checkout() ) return; //alx359
        // Unhook WooCommerce functions
        if ( doing_action( 'woocommerce_checkout_init' ) || did_action( 'woocommerce_checkout_init' ) ) {
            remove_action( 'woocommerce_checkout_billing', array( WC()->checkout, 'checkout_form_billing' ), 10 );
            remove_action( 'woocommerce_checkout_shipping', array( WC()->checkout, 'checkout_form_shipping' ), 10 );
        }
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Diego Versiani

    (@diegoversiani)

    5 months, 2 weeks ago

    Hi @alx359,

    Thanks for reporting this issue. We are investigating this but cannot yet consistently reproduce this issue.

    This seems related to a compatibility issue with the plugin WooCommerce PayPal Payments, as reported by another customer.

    1. Could you confirm whether you are also using the plugin WooCommerce PayPal Payments on your website?

    2. Could you run a plugin conflict test to find out which plugin or theme might be conflicting with Fluid Checkout on your setup?

    Basically, you temporarily deactivate all plugins except for WooCommerce and Fluid Checkout, then re-activate each plugin one by one until you find one that causes the issue. Ideally this should be done in a test/staging copy of your website. You can find more specific instructions in the article below from WooCommerce:
    https://docs.woocommerce.com/document/how-to-test-for-conflicts/

    Once we know what plugin or theme is causing this compatibility issue with Fluid Checkout, then we can work on fixing it.

    Kind regards,
    Diego.

    Thread Starter alx359

    (@alx359)

    5 months, 2 weeks ago

    @diegoversiani, thanks for replying. Your suggestion appears correct. Disabling “Payment Plugins for PayPal WooCommerce” by mrclayton the issue so far goes away.

    Plugin Author Diego Versiani

    (@diegoversiani)

    5 months, 2 weeks ago

    Hi @alx359,

    We were still not able to reproduce the issue on our local development environment using either of the PayPal plugin, whether using the plugin “Payment Plugins for PayPal WooCommerce” or the official plugin “WooCommerce PayPal Payments”.

    In any case, we’ve made some changes to the plugin to try to mitigate this problem but cannot validate whether it would fix the issue for you and the other customer who reported this issue.

    1. Could you try using one of the two alpha versions below, and let us know which one fixes the issue, if any? Please note that these alpha versions are early development versions for this fix and are not ready for use on a Live/Production environment.

    If the problem persists after updating to these alpha versions, trying one at a time, there might be some other component or configuration which triggers this issue.

    2. Could you prepare a test/staging copy of your website where this problem can be reproduced, and contact us on our main support channel to share access to your staging site so we can continue with the investigation? Please do not share any sensitive information on this public support forum.

    Kind regards,
    Diego.

    Thread Starter alx359

    (@alx359)

    5 months, 2 weeks ago

    Hi @diegoversiani, thank you for providing the alphas. Alpha-1 still produces the same issue for me. Alpha-2 though seems to work.

    Plugin Author Diego Versiani

    (@diegoversiani)

    5 months, 2 weeks ago

    Hi @alx359,

    Thanks for confirming. We have now integrated solution from alpha-2 into the code for the next patch version which will be released in the next couple of days.

    For now, you could also use the beta version from the link below, which should be ready for production use. As always, just make sure to take a full backup of your website before installing this update, in case anything goes wrong.

    I’m closing this ticket for now. If you need further assistance related to this issue, simply reply to this message to re-open it.

    Kind regards,
    Diego.

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.