• Resolved pozyczkabez

    (@seo-top)


    Fatal error: Uncaught Error: Cannot unset string offsets in /public_html/wp-content/plugins/flexible-checkout-fields/classes/plugin.php:247 Stack trace: #0 /public_html/wp-includes/class-wp-hook.php(324): Flexible_Checkout_Fields_Plugin->woocommerce_get_country_locale_base(Array) #1 /public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters(Array, Array) #2 /public_html/wp-content/plugins/woocommerce/includes/class-wc-countries.php(1651): apply_filters(‘woocommerce_get…’, Array) #3 /public_html/wp-content/plugins/woocommerce/includes/class-wc-frontend-scripts.php(549): WC_Countries->get_country_locale() #4 /public_html/wp-content/plugins/woocommerce/includes/class-wc-frontend-scripts.php(465): WC_Frontend_Scripts::get_script_data(‘wc-address-i18n’) #5 /home/sklepsport/domains/sklep-sp in /public_html/wp-content/plugins/flexible-checkout-fields/classes/plugin.php on line 247

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hi there @seo-top, thank you for reaching out.

    Based on the error message, there seems to be a conflict with the Flexible Checkout Fields Plugin.

    Here’s how you can try to resolve this issue:

    1. Deactivate the Flexible Checkout Fields Plugin. You can do this by going to your WordPress dashboard, clicking on ‘Plugins’, and then ‘Deactivate’ next to the Flexible Checkout Fields Plugin.

    2. Once deactivated, check if your site is working properly. If it is, the issue is definitely with the plugin.

    3. Contact the plugin developer with the error message you provided. They should be able to provide a solution or update the plugin to fix the issue.

    You can also find more details on how to perform a conflict test from our guide.

    Let us know how it goes. Cheers!

    Try option 3 below (it’s an easy setting to apply and test):

    What action should I take?

    • Plesk already has a help article targeting this issue, identifying Comodo rule with ID 218500 being false-positively triggered when Woocommerce 8.5 is in use. They recommend disabling the rule following the steps on their page.
    • Check with your host to see if ModSecurity is enabled. If that is the case, you may ask your host to adjust the firewall rules to allow the cookies set by Woo’s Order Attribution feature. You can find more information about the cookies used by this feature in our documentation.
    • If the above doesn’t work for you, disable the Order Attribution feature to prevent future users from seeing the 403 errors by going to WooCommerce > Settings > Advanced > Features and toggling the Order Attribution feature off.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘New update 8.5.1 still errors’ is closed to new replies.