• Resolved Elliot

    (@mladja11)


    Hi,

    For some reason, this plugin conflicts with Fluent CRM, producing a fatal error on the checkout page.

    I have tested it with only WooCommerce, CartFlows, and Fluent CRM enabled, with all other plugins disabled.

    I also used the Storefront theme to eliminate any theme conflicts.

    Here is the error captured:

    PHP message: PHP Fatal error: Uncaught TypeError: array_diff(): Argument #1 ($array) must be of type array, string given in /public_html/wp-content/plugins/cartflows/modules/checkout/classes/class-cartflows-checkout-fields.php:620\nStack trace:\n#0 /public_html/wp-content/plugins/cartflows/modules/checkout/classes/class-cartflows-checkout-fields.php(620): array_diff()\n#1 /public_html/wp-includes/class-wp-hook.php(324): Cartflows_Checkout_Fields->label_skins_fields_customization()\n#2 /public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters()\n#3 /public_html/wp-content/plugins/woocommerce/includes/class-wc-checkout.php(300): apply_filters()\n#4 /public_html/wp-content/plugins/cartflows/woocommerce/template/checkout/form-checkout.php(34): WC_Checkout->g…'
    
    

    I tested it with PHP versions 8.2 and 7.4 without noticing any differences. In other words, the error persists, regardless of the PHP version used.

Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Support Shravan Bhaskaravajjula

    (@bhshravankumar)

    Hello @mladja11,

    Does enabling CartFlows and FluentCRM trigger this scenario, or are there any specific steps to reproduce it? The issue seems to be related to the CartFlows checkout form fields data. We will try reproducing this issue, but if there are any specific steps to reproduce it, please let us know.

    Thread Starter Elliot

    (@mladja11)

    Hi,

    Yes, only FluentCRM and CartFlows.

    It has something to do with store checkout. That is what e have discovered today. If we disable store checkout, then the checkout loads as expected, if we enable it, then it produces that critical error.

    So, what you need is Latest version of both mentioned plugins and WooCommerce. Just add a product to cart and then proceed to checkout. That is all you need to reproduce the error.

    We are using Cloudways and we investigated further with their support and they confirmed that it has nothing to do with server stuff. So we excluded Varnish, Redis, Cloudflare. PHP versions and those kind of things…

    I just encountered this same error:
    PHP Fatal error: Uncaught TypeError: array_diff(): Argument #1 ($array) must be of type array, string given in /..plugins/cartflows/modules/checkout/classes/class-cartflows-checkout-fields.php on line 620

    Meanwhile nothing new was installed, I only created a new funnel, and I wanted to edit the checkout page when this error popped up. Is there a solution in view?

    I can confirm there is a conflict with FluentCRM and CartFlow. I have a staging site, there is still the old version of FluentCRM 2.8.45 installed with CartFlow 2.0.8. On the live websiter there is FluentCRM 2.9 installed.

    I will also inform the WPManageTeam

    Thanks,

    Edy

    The WPmanage Team throw the ball back to the CartFlow team. Not helpful. If it helps I can give you access to my staging site where you can troubleshoot it.

    Thread Starter Elliot

    (@mladja11)

    Well, I can not wait anymore. My solution to this problem is this: https://www.checkoutwc.com/

    Plugin Support Shravan Bhaskaravajjula

    (@bhshravankumar)

    Hello @mladja11, @fafa24 and @dagenius20,

    Apologies for any inconvenience caused.

    I have installed the latest FluentCRM free and Pro plugins. After activating these plugins, I tried working with CartFlows but did not encounter any issues with the store checkout or the normal CartFlows checkout. I must be missing something to replicate the error scenario.?

    Please refer to this screen recording:?https://bsf.d.pr/v/3KSy4B?and let me know if I am missing anything to replicate the error scenario so that I can check again and try resolving the conflict ASAP.

    Looking forward to hearing from you.

    Plugin Support Shravan Bhaskaravajjula

    (@bhshravankumar)

    Hello?@mladja11,?@fafa24?and?@dagenius20,

    Please review the screen recording and let us know if we are missing anything needed to replicate the error scenario.

    Thank you for your understanding and cooperation.

    Plugin Support Shravan Bhaskaravajjula

    (@bhshravankumar)

    Hello?@mladja11,?@fafa24?and?@dagenius20,

    It appears that FluentCRM is causing a conflict when you enable the ‘Enable Subscription Checkbox on WooCommerce Checkout Page’ setting, please refer to this screenshot: https://bsf.d.pr/i/2keDok.

    This adds a custom form field not included by CartFlows, resulting in a conflict. Disabling this option resolves the issue with CartFlows checkout.

    Shared this information with our internal team, once we hear from the team we will update you.

    Plugin Support Shravan Bhaskaravajjula

    (@bhshravankumar)

    Hello?@mladja11,?@fafa24?and?@dagenius20,

    Update: Our developers have fixed this issue. The fix will be included in the next update.

    Hope this helps.

    Thread Starter Elliot

    (@mladja11)

    Hi guys. Sorry for the delay.

    OK Great!

    I still have the sandboxes for this project. However, when I checked earlier today, after seeing @bhshravankumar’s post mentioning that it works on his side, I was still encountering the error on my end.

    Plugin Support Aamir

    (@aamiribsf)

    Hello @mladja11,

    It seems you might have missed the last response from my colleague. We would like to inform you that Our developers have fixed this issue. The fix will be included in the next update.

    Best Regards,

    Thread Starter Elliot

    (@mladja11)

    No, no. I did not mean that. I meant my on my current setup. It is fine. I have tested it today with latest versions of all plugins and it works normally.

    I can confirm it works and I will switch back now to CF.

    Plugin Support Shravan Bhaskaravajjula

    (@bhshravankumar)

    Hello @mladja11,

    Thanks for the update, I hope everything is working smoothly now.

    Let us know if we could be of any further assistance.?

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