• Resolved crystalpayton

    (@crystalpayton)


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

    First, visit your website (https://www.kmscompany.com/) and check for any visible issues. Next, visit the page where the error was caught (https://www.kmscompany.com/wp-admin/admin.php?page=inspire_checkout_fields_settings) and check for any visible issues.

    When seeking help with this issue, you may be asked for some of the following information:
    WordPress version 6.0.1
    Active theme: KMS (version 1.0.0)
    Current plugin: WooCommerce Stripe Gateway (version 6.5.0)
    PHP version 7.4.15

    Error Details
    =============
    An error of type E_ERROR was caused in line 664 of the file /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/woocommerce-gateway-stripe/woocommerce-gateway-stripe.php. Error message: Uncaught Error: Call to a member function get_upe_enabled_payment_method_ids() on null in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/woocommerce-gateway-stripe/woocommerce-gateway-stripe.php:664
    Stack trace:
    #0 /opt/bitnami/apps/wordpress/htdocs/wp-includes/class-wp-hook.php(309): WC_Stripe->checkout_update_email_field_priority()
    #1 /opt/bitnami/apps/wordpress/htdocs/wp-includes/plugin.php(191): WP_Hook->apply_filters()
    #2 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/woocommerce/includes/class-wc-countries.php(1616): apply_filters()
    #3 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/flexible-checkout-fields/src/Settings/Form/EditFieldsForm.php(71): WC_Countries->get_address_fields()
    #4 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/flexible-checkout-fields/src/Settings/Form/EditFieldsForm.php(29): WPDesk\FCF\Free\Settings\Form\EditFieldsForm->get_section_form_data()
    #5 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/flexible-checkout-fields/src/Settings/Form/FormIntegrat

    from flexible checkout fields for woocommerc:

    However, the error is not in our plugin, but probably in the WooCommerce Stripe Payment Gateway plugin. Why do I think so? Our plugin retrieves data from WooCommerce using generally available functions (which is described in this documentation). The WooCommerce Stripe Payment Gateway plugin integrates with WooCommerce and probably does not handle some exception that happened.
    
    In the error message you are also given the path to our plugin code, because it is our plugin that calls the WooCommerce function. When this function is called, WooCommerce performs certain operations with which the WooCommerce Stripe Payment Gateway plugin integrates. And then the error occurs. The error does not appear in the code of our plugin, only our plugin triggers an action followed by an error in the WooCommerce Stripe Payment Gateway plugin.
    
    In this case, please contact the WooCommerce Stripe Payment Gateway plugin support. Remember, however, that we are open to cooperation and we remain at your disposal in case of additional questions.

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter crystalpayton

    (@crystalpayton)

    Tried another custom checkout field plugin and still run into this issue

    Hi @crystalpayton,

    Thanks for reaching out!

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

    In order for us to understand your site properly, can you please share your System Status Report, that will help us further troubleshoot.

    You can find it via WooCommerce > Status. Select “Get system report” and then “Copy for support”. Once you’ve done that, you can paste it into your reply here.

    Plugin Support Kaushik S. a11n

    (@kaushiksomaiya)

    Hi there @crystalpayton!

    This is currently reported as a bug (compatibility with other plugins) and is being investigated here: https://github.com/woocommerce/woocommerce-gateway-stripe/issues/2394

    I’d suggest downgrading to version 6.4.3 and see if that helps!

    You could also comment your thoughts and suggestions on the Github bug report directly.

    I hope this helps! ??

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Fatal Error’ is closed to new replies.