• Resolved Thane

    (@thanewest)


    Latest version of this plugin was updated, but I stayed on the previous version of Woocommerce and it caused my entire site to show whitescreen with this error message:
    Error thrown
    Class ‘WC_Gateway_Amazon_Advanced’ not found

    I don’t update Woocommerce when it’s a major version update, not until after a few weeks when they’ve rolled out fixes for bugs, and give time for addon plugins to get updated as well… This is a normal update strategy, so probably a lot of other users are going to run into this.

Viewing 4 replies - 16 through 19 (of 19 total)
  • Plugin Support Christian

    (@christian1983)

    Hey @jferezy,

    We are in process of testing with PHP8 but we are not having issues. Can you send us the logs, please?

    Best,
    Christian

    Sure:

    This is when I have PHP8.1:

    Fatal error: Uncaught TypeError: call_user_func_array(): Argument #1 ($callback) must be a valid callback, class WC_Amazon_Payments_Advanced does not have a method “checkout_message” in /home/katrinat/public_html/wp-includes/class-wp-hook.php:307

    When I turn back to 7.4 – I get a warning, but not fatal.

    <b>Warning</b>: call_user_func_array() expects parameter 1 to be a valid callback, class ‘WC_Amazon_Payments_Advanced’ does not have a method ‘checkout_message’ in <b>/home/katrinat/public_html/wp-includes/class-wp-hook.php</b> on line <b>307</b><br />

    Maybe I am missing something?

    Plugin Support Christian

    (@christian1983)

    Hey @jferezy

    Do you already migrate to V2 keys? can you share a full screenshot of your Amazon Settings? you can use https://imgbb.com

    I will test it on our side and get back to you on this thread.

    Best,
    Christian

    Plugin Support Christian

    (@christian1983)

    Hey @jferezy,

    After migrating to V2 keys and updating to PHP8.1 no fatal errors were present.

    Can you check please if you finished the V2 migration?

    Best,
    Christian

Viewing 4 replies - 16 through 19 (of 19 total)
  • The topic ‘Critical Sitewide Error’ is closed to new replies.