• Resolved gkartikey

    (@gkartikey)


    Hi,

    I just updated to the latest version of the plugin 1.6.21, and I received this email from WordPress.

    Howdy!

    Since WordPress 5.2, there is a built-in feature that detects when a plugin or theme causes a fatal error on your site and notifies you with this automated email.

    In this case, WordPress caught an error with one of your plugins, WooCommerce PayPal Checkout Gateway.

    But, the site seems to be functioning normally, so I reverted to the old version, in its a back end issue in the payment processor. So, what can be done now?

Viewing 13 replies - 1 through 13 (of 13 total)
  • Joey – a11n

    (@jricketts4)

    @gkartikey – do you see any fatal error logs in ‘WP Dashboard > WooCommerce > Status > Logs‘?
    If any logs were created for this error, can you post those here?

    – Joey

    Thread Starter gkartikey

    (@gkartikey)

    @jricketts4 Can I email you the fatal error log?

    Joey – a11n

    (@jricketts4)

    I would suggest using a service like this: https://send.firefox.com/

    – Joey

    Thread Starter gkartikey

    (@gkartikey)

    Joey – a11n

    (@jricketts4)

    @gkartikey – I’ve actually never seen this error before, which can mean one of two things:

    1. It’s a new error in our plugin.
    2. There’s a conflict occurring.

    To figure out the next best step, there are a few things I’ll need to move forward:

    1. Send a copy of your system status report: WP Dashboard > WooCommerce > Status > ‘Get system report’ (you can use Firefox Send)
    2. Navigate to: WP Dashboard > WooCommerce > Settings > Payments > PayPal Checkout
    1. Are there any values filled in the ‘Live API Certificate’ field?
    • Plugin/theme conflict testing (will include details below).
    • —-

      Conflict Testing

      The best way to determine this is to:

    • Temporarily switch your theme to Storefront
    • Disable all plugins except for WooCommerce
    • Repeat the action that is causing the problem

    If you’re not seeing the same problem after completing the conflict test, then you know the problem was with the plugins and/or theme you deactivated. To figure out which plugin is causing the problem, reactivate your other plugins one by one, testing after each, until you find the one causing conflict. You can find a more detailed explanation on how to do a conflict test here.

    —-

    Let me know once you can answer/send/confirm the above 3 items. 😁

    – Joey

    Thread Starter gkartikey

    (@gkartikey)

    @jricketts4 – I rollbacked the plugin, as it was my live store. Now, do you want me to update the plugin and then send you the details?

    I can do that as I’ve just made a staging website for plugin update issues. So, just tell me how do you need it, then I’ll do the conflict testing part.

    • This reply was modified 4 years ago by gkartikey.
    Plugin Support Doug – a11n

    (@dougaitken)

    Automattic Happiness Engineer

    Hey @gkartikey

    Absolutely! If you have a staging site, please update everything again and if you’re able to go through that conflict testing, that would be fantastic.

    For more detailed instructions about conflict testing, check out this – https://docs.woocommerce.com/document/how-to-test-for-conflicts

    Please let us know how that goes.

    Thanks,

    Thread Starter gkartikey

    (@gkartikey)

    Hi,

    @dougaitken @jricketts4

    I’ve done the first steps.
    1. Updated the plugin on a staging website, added the error in the link below. And the system report as well in the same file.
    2. Yes, there are values in the ‘Live API Certificate.’

    Link: https://send.firefox.com/download/c6550793865f6511/#RRy7TjDHtz4cmBYkNZ7VMg

    By the time you check this, I’ll do the conflict testing, and will reply once it is done,

    Thread Starter gkartikey

    (@gkartikey)

    Hi,

    I did the plugin conflict testing. I arrived at the following plugin list, which are creating errors:

    Active Plugins – If I deactivate any of the three plugins, the error was not shown when updating to 1.6.21, i.e. the error was revealed only when all the three plugins were active:
    1. AliDropship Woo Plugin
    2. Finale – WooCommerce Sales Countdown Timer
    3. Wordfence Security

    Harmless Active Plugins:
    1. Really Simple SSL
    2. WooCommerce PayPal Checkout Gateway
    3. WooCommerce
    4. WP Rollback

    I am still not able to understand how this is possible, but I arrived at this after performing numerous iterations. I am attaching the Error Log file(all the error instances while Conflict Testing) and the WOO system report link:
    https://send.firefox.com/download/68a2ca93bf3ee6ec/#NFF4DvWZZJCUx9Tx44WxNg

    Thread Starter gkartikey

    (@gkartikey)

    @dougaitken @jricketts4

    Please update asap on this issue!

    Plugin Support Doug – a11n

    (@dougaitken)

    Automattic Happiness Engineer

    Hey @gkartikey

    Active Plugins – If I deactivate any of the three plugins, the error was not shown when updating to 1.6.21, i.e. the error was revealed only when all the three plugins were active:
    1. AliDropship Woo Plugin
    2. Finale – WooCommerce Sales Countdown Timer
    3. Wordfence Security

    To confirm – having only WooCommerce and the PayPal Checkout active presents no problem? If you can have WooCommerce and the PayPal Checkout plugin active with no errors then thise sounds like a conflict with the plugins you mention.

    I’d recommend starting with only WooCommerce, a default theme, and the PayPal Checkout plugin active then reactivate one-by-one those other plugins.

    Thanks,

    Thread Starter gkartikey

    (@gkartikey)

    Hi,

    Yes, I figured that and have forwarded the query to the respective plugin support. Thanks. πŸ™‚

    Plugin Support Doug – a11n

    (@dougaitken)

    Automattic Happiness Engineer

    Hi @gkartikey

    I appreciate you looping back to us here.

    I will mark this ticket as Resolve now, but please do open a new one if you need any more help!

    Thanks,

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Your Site is Experiencing a Technical Issue’ is closed to new replies.