• Resolved mikejandreau

    (@mikejandreau)


    I’m testing out the free version of your plugin, but find that when I enable CheckoutWC, there’s an error showing a conflict with it:

    Fatal error: Uncaught Error: in_array(): Argument #2 ($haystack) must be of type array, string given
    in /home/931063.cloudwaysapps.com/cfnskvdbee/public_html/wp-content/plugins/woocommerce-checkout-manager/lib/view/frontend/class-fields-register.php on line 71

    If I disable their plugin, yours works fine. However, when I look at woocommerce-checkout-manager/lib/view/frontend/class-fields-register.php, there is no haystack on line 71.

    Can you help? I’d like to buy your plugin, but not if I can’t get it to work.

    The whole stack error, in case that’s helpful:

    Call stack:

    in_array()
    wp-content/plugins/woocommerce-checkout-manager/lib/view/frontend/class-fields-register.php:71
    QuadLayers\W\V\F\Fields_Register::add_billing_fields_beta()
    wp-includes/class-wp-hook.php:324
    WP_Hook::apply_filters()
    wp-includes/plugin.php:205
    apply_filters()
    wp-content/plugins/woocommerce/includes/class-wc-checkout.php:300
    WC_Checkout::get_checkout_fields()
    wp-content/plugins/woo-stripe-payment/includes/wc-stripe-functions.php:1293
    wc_stripe_get_checkout_fields()
    wp-content/plugins/woo-stripe-payment/includes/class-wc-stripe-frontend-scripts.php:129
    WC_Stripe_Frontend_Scripts::localize_scripts()
    wp-includes/class-wp-hook.php:324
    WP_Hook::apply_filters()
    wp-includes/class-wp-hook.php:348
    WP_Hook::do_action()
    wp-includes/plugin.php:517
    do_action()
    wp-includes/script-loader.php:2224
    wp_print_head_scripts()
    wp-includes/class-wp-hook.php:324
    WP_Hook::apply_filters()
    wp-includes/class-wp-hook.php:348
    WP_Hook::do_action()
    wp-includes/plugin.php:517
    do_action()
    wp-includes/general-template.php:3064
    wp_head()
    wp-content/plugins/checkout-for-woocommerce/includes/Loaders/Redirect.php:239
    Objectiv\P\C\L\Redirect::cfw_wp_head()
    wp-content/plugins/checkout-for-woocommerce/includes/Loaders/Redirect.php:201
    Objectiv\P\C\L\Redirect::head()
    wp-content/plugins/checkout-for-woocommerce/includes/Loaders/Redirect.php:57
    Objectiv\P\C\L\Redirect::checkout()
    wp-content/plugins/checkout-for-woocommerce/includes/Loaders/Redirect.php:386
    Objectiv\P\C\L\Redirect::template_redirect()
    wp-content/plugins/checkout-for-woocommerce/sources/php/functions.php:1825
    {closure}()
    wp-includes/class-wp-hook.php:324
    WP_Hook::apply_filters()
    wp-includes/class-wp-hook.php:348
    WP_Hook::do_action()
    wp-includes/plugin.php:517
    do_action()
    wp-includes/template-loader.php:13
    require_once()
    wp-blog-header.php:19
    require()
    index.php:17

    If I remove the checks at lines 71 and 99, everything works.

    What does that code actually do?

    		if ( isset( $fields['shipping']['shipping_address_2']['label_class'] ) && in_array( 'screen-reader-text', $fields['shipping']['shipping_address_2']['label_class'], true ) ) {
    $fields['shipping']['shipping_address_2']['label_class'] = array_filter(
    $fields['shipping']['shipping_address_2']['label_class'],
    static function ( $class ) {
    return 'screen-reader-text' !== $class;
    }
    );
    }
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support jmatiasmastro

    (@jmatiasmastro)

    @mikejandreau Hi mate,

    Thank you for reaching out and providing detailed information about the issue you’re experiencing.

    From what we understand, it seems there is a compatibility conflict between our plugin, , and the CheckoutWC plugin. Based on your description, it appears that both plugins modify the checkout page, which may be causing the error.

    To help us investigate further, could you please provide the following information?

    1. The version of our plugin that you are using.
    2. Your WordPress version.
    3. Your WooCommerce version.
    4. A brief description of the main functionality of the CheckoutWC plugin on your site (e.g., what changes it makes to the checkout process).

    While we strive to ensure broad compatibility, we cannot guarantee that our plugin will work seamlessly with all third-party plugins, especially those that make significant modifications to the same area of functionality. That said, with the information you provide, we may be able to explore potential solutions or improvements on our end

    Best regards, Quadlayers Support Team.

    Thread Starter mikejandreau

    (@mikejandreau)

    1. The version of our plugin that you are using – Free ?7.6.2, Pro 7.4.5
    2. Your WordPress version – 6.7.1
    3. Your WooCommerce version – 9.4.2
    4. A brief description of the main functionality of the CheckoutWC plugin on your site (e.g., what changes it makes to the checkout process) – It streamlines checkout into a more enjoyable experience and removes header and footer to prevent navigating away from the checkout process.
    Plugin Support jmatiasmastro

    (@jmatiasmastro)

    @mikejandreau

    Hi mate, thanks for updating your ticket, we recommend submitting a support ticket through the following link:?https://urbiport1.atlassian.net/servicedesk/customer/portal/2.

    This will allow us to investigate further.

    Best regards, Quadlayers Support Team.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.