• Resolved pgray

    (@pgray)


    Greetings,

    There seems to be a conflict with Cartflows plugin. On the checkout page when the payment button is clicked the “processing” gif keeps churning for a while before an error is returned.

    The order processes fine but it appears that the transfer to thank you page is interrupted by the error.

    We have disabled this plugin. Hope you will fix the error because we would like to use this plugin again.

    Thanks!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support WebToffee Support

    (@webtoffeesupport)

    Hi pgray,

    Thanks for reaching out.

    We were unable to replicate the issue on our end. Please make sure you are using the latest version 4.5.3 of the plugin. Additionally, kindly share the following details for better understanding of the issue.

    • Screen recording of the error displayed when the page loads to “Thank you” page.
    • Fatal error log (WooCommerce > Status > Logs > Fatal errors).
    • WooCommerce system status report (WooCommerce > Status > System status > Get system report).

    Kindly mask sensitive information when sharing the screen recording requested above. You may share the details via?this link?if you have any privacy concerns.

    Thread Starter pgray

    (@pgray)

    Thanks for responding.

    • The control doesn’t transfer to the Thank You page. The error is displayed on the checkout page after sometime
    • Here’s the error from the error log. It disappears when pdf invoices plugin is deactivated

      [Sun Jun 30 20:09:35.923547 2024] [proxy_fcgi:error] [pid 19583:tid 139928876832512] [client …] AH01071: Got error ‘PHP message: PHP Warning: Undefined property: WC_Gateway_PayPal_Pro_Subscriptions_AngellEYE::$wc_pre_30 in …/wp-content/plugins/paypal-for-woocommerce/classes/subscriptions/wc-gateway-paypal-pro-subscriptions-angelleye.php on line 86; PHP message: is_internal_meta_key was called incorrectly. Generic add/update/get meta methods should not be used for internal meta data, including “_payment_tokens”. Use getters and setters. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_PayPal_Pro_Subscriptions_AngellEYE->process_payment, WC_Gateway_PayPal_Pro_AngellEYE->process_payment, WC_Gateway_PayPal_Pro_AngellEYE->do_payment, WC_Gateway_PayPal_Pro_Subscriptions_AngellEYE->save_payment_token, WC_Data->get_meta, WC_Data->is_internal_meta_key, wc_doing_it_wrong. This message was added in version 3.2.0.’, referer: …/checkout-2/

    Hope this helps.

    Plugin Support WebToffee Support

    (@webtoffeesupport)

    Hi pgray,

    We reviewed the information you provided. We see that the error log you sent belongs to the wc-gateway-paypal-pro-subscriptions-angel plugin. Please check this with the thier support team. Additionally, please provide a screen recording of a test order placed with our plugin installed and the WooCommerce system status report (WooCommerce > Status > System status > Get system report) for better understanding. You can share the screen recording?via this link.

    Thread Starter pgray

    (@pgray)

    Thanks for your response. I understand that the error is showing in Paypal for Woo but if Woo pdf invoices is deactivated the error disappears – in other words we can process orders in CartFlows + Paypal for Woo without any problems. In fact, till the latest update in your plugin things were working fine.

    I am reporting a conflict between these two plugins. Please test Woo pdf invoice with Paypal for Woo and CartFlows. If they work fine, please let me know and I will provide the specifics of our installation.

    Plugin Support WebToffee Support

    (@webtoffeesupport)

    Hi pgray,

    We have not tested compatibility with the Wc-gateway-paypal-pro-subscriptions-angel plugin. We will consider checking the feasibility of making the plugin compatible in our future releases. Thank you for understanding.

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