latest update 2.0 ruined my site

  • I just updated to the latest version and cart page , as well as the checkout page are totally ruined.

    It is also written that a critical error occured !

    (I use the Woodmart theme)

    Sorry but this the second time I have problems when updating, last time was with the 1.7.0 version not adding the fee.

    I had to roll back to the 1.7.1 version.

    https://ibb.co/7prHQRR

    • This topic was modified 1 year, 9 months ago by jkont.
    • This topic was modified 1 year, 9 months ago by jkont.
    • This topic was modified 1 year, 9 months ago by jkont.
    • This topic was modified 1 year, 9 months ago by jkont.
    • This topic was modified 1 year, 9 months ago by Jan Dembowski. Reason: Decapped titlle. Don't yell

    The page I need help with: [log in to see the link]

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

  • I also had an issue with 2.0 update and I got a PHP fatal error in checkout page:

    PHP Fatal error: ?Uncaught TypeError: array_key_exists(): Argument #2 ($array) must be of type array, bool given in …/wp-content/plugins/simple-cod-fee-for-woocommerce/simple-cod-fee-for-woocommerce.php:358

    I solved it by 1) checking “Accept COD if the order is virtual” in Cash on delivery settings (Woocommerce > Payments > Cash on delivery). That is because WC()->payment_gateways->get_available_payment_gateways() in includes/admin-menu.php did not return cod without the previous being checked (no idea why). So, after that, the admin page was able to load, and 2) I clicked the Save button on the 2.0 admin menu. After the previous steps, I did not get fatal errors on checkout/cart pages.

    Also, I wonder if the return at line 21 in includes/admin-menu.php is necessary because it prevents the settings from loading.

    Plugin Author Andreas Sofantzis

    (@asofantzis)

    In version 2.0 it is critical to visit the new settings page and save the new settings.

    The error I see above means that COD was not enabled. Also the returnat line 21 in?includes/admin-menu.php is intended to be there to prevent the COD settings from showing if native COD is not enabled in the WC settings. Will definitely look into it once again.

    If you have any further question feel free to email me at support[at]83pixel.com

    Sorry for the frustration this update caused

    Plugin Author Andreas Sofantzis

    (@asofantzis)

    I see what this might come from.

    If you disable and re-enable the plugin these errors will be solved. Will rewrite some code to run without this unnecessary step of disabling/enabling

    Plugin Author Andreas Sofantzis

    (@asofantzis)

    Made an update fix that will migrate most settings once the plugin is updated. To be 100% sure go the new settings page and save again

    2.0.2 seems fine for me.

    Thanks for the quick update!

    Thread Starter jkont

    (@jkont)

    Is the 1.7.1 version lighter than 2.x ?

    Plugin Author Andreas Sofantzis

    (@asofantzis)

    @markoskon very glad to hear that.

    @jkont lighter in which way? In size? No in size its couple of KB more thought it won’t affect the loading speed if that’s your concern. It’s the same code as before in the frontend.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘latest update 2.0 ruined my site’ is closed to new replies.