• Resolved Daniel Chase

    (@riseofweb)


    [23-Jan-2024 15:37:06 UTC] Payment gateway with handle 'wc-poynt-checkout-block' has been deactivated in Cart and Checkout blocks because its dependency 'poynt-collect' is not registered. Read the docs about registering assets for payment methods: https://github.com/woocommerce/woocommerce-blocks/blob/060f63c04f0f34f645200b5d4da9212125c49177/docs/third-party-developers/extensibility/checkout-payment-methods/payment-method-integration.md#registering-assets

    I just updated it to the latest version. Now, every time the checkpage is visited, it sends the above notice.

    Also on the Plugins page (plugins.php). It lists “Configure” twice under your plugin. The second “Configure” link goes to “/wp-admin/admin.php?page=wc-settings&tab=checkout&section=pay_in_person” – I do not have pay in person enabled. The page displays, “There has been a critical error on this website. Please check your site admin email inbox for instructions.”

    The PHP error created when visiting that page is:

    [23-Jan-2024 15:43:37 UTC] PHP Fatal error: Uncaught Error: Call to a member function get_base_country() on null in /wp-content/plugins/woocommerce-shipping-fedex/includes/data/data-service-codes.php:13
    Stack trace: 0 /wp-content/plugins/woocommerce-shipping-fedex/includes/class-wc-shipping-fedex.php(120): include() 1 /wp-content/plugins/woocommerce/includes/class-wc-shipping.php(199): WC_Shipping_Fedex->__construct() 2 /wp-content/plugins/woocommerce/includes/class-wc-shipping.php(177): WC_Shipping->register_shipping_method('WC_Shipping_Fed…') 3 /wp-content/plugins/godaddy-payments/src/Gateways/PayInPersonGateway.php(450): WC_Shipping->load_shipping_methods() 4 /wp-content/plugins/godaddy-payments/src/Gateway in //wp-content/plugins/woocommerce-shipping-fedex/includes/data/data-service-codes.php on line 13
Viewing 15 replies - 1 through 15 (of 23 total)
  • Plugin Support Zach

    (@zachskyverge)

    Hello there @riseofweb ,

    Thank you for reaching out about our plugin, Godaddy Payments! I’m happy to assist you with this. ??

    I am sorry to hear about the issues you are seeing with the plugin. Given that the fatal error involves the WooCommerce Fedex Shipping plugin. Could you try disabling the plugin and check if there is still multiple configure buttons for the gateway? Also would it be possible to send a screenshot of the current settings for the payment method. Please be sure to blur or block any account details.

    Best,

    Thread Starter Daniel Chase

    (@riseofweb)

    Here is the screenshot. https://ibb.co/FVJZYzS Note that the underlined links create a critical error message.

    I have disabled the WooCommerce Fedex Shipping plugin and the error went away. The multiple configure links still remained.

    Plugin Support amberskyverge

    (@amberskyverge)

    Hey there,

    Amber here, filling in for Zach. I’m happy to hear that when you disabled the WooCommerce Fedex Shipping plugin, the errors went away. That definitely means that the error is coming from that plugin and you may need to reach out to them to find out why that is.

    Thank you for also sending the screenshot of the WooCommerce Payment page, that was helpful as well.

    In regards to GoDaddy payments, I wasn’t able to see the full error message. Would you be able to send us a screenshot of the error you are seeing?

    All the best,

    Amber

    eric4

    (@eric4)

    Same error after upgrade to Godaddy Payments 1.7.0

    Payment gateway with handle ‘wc-poynt-checkout-block’ has been deactivated in Cart and Checkout blocks because its dependency ‘poynt-collect’ is not registered. Read the docs about registering assets for payment methods: https://github.com/woocommerce/woocommerce-blocks/blob/060f63c04f0f34f645200b5d4da9212125c49177/docs/third-party-developers/extensibility/checkout-payment-methods/payment-method-integration.md#registering-assets

    eric4

    (@eric4)

    Disable the plugin to remove the error.

    Rolled back to Version 1.6.2 that fixed the problem.

    Plugin Support amberskyverge

    (@amberskyverge)

    Hey there,

    Thank you for keeping us updated with what was happening on your end. That is interesting to know that when you rolled back the plugin to version 1.6.2 that it fixed the issue. I will definitely let my team know this and see what we need to do moving forward so that this doesn’t happen and we can have users update the plugin since its ideal to have merchants on the newest version.

    Is there anything else I can assist you with?

    All the best,

    Amber

    Plugin Support amberskyverge

    (@amberskyverge)

    Hey there,

    It has been a long time since we heard from you, so I’m going to mark this topic as resolved. I did want to also let you know that we have created this issue as a bug report, so that we can get this fixed. I sincerely appreciate you bringing this to our attention.

    If you’re experiencing additional issues please take a look at our FAQs for more information and create a new thread if you have further questions.

    Thanks,
    Amber ??

    Plugin Support amberskyverge

    (@amberskyverge)

    Hey there,

    My team is working on this issue, and they were wondering if you’d be interested in answering some questions for them in regards to what was happening on your end so they can get this resolved. Would you mind answering some questions?

    All the best,
    Amber ??

    Thread Starter Daniel Chase

    (@riseofweb)

    Sure. Ask away.

    Sure. I also see this error for quite a while.

    [08-Feb-2024 06:37:42 UTC] PHP Fatal error: Uncaught Error: Call to a member function get_payment_method() on bool in /home//public_html/wp-content/plugins/godaddy-payments/src/Gateways/PayInPersonGateway.php:180

    Plugin Support amberskyverge

    (@amberskyverge)

    Hey,

    Thank you so much for offering to help, we sincerely appreciate it. I will also pass along this error that you’re seeing to them as well. Here are a few questions we have.

    First, where are you seeing the console error regarding the wc-poynt-checkout-block being deactivated?

    Second, are you using cart and checkout blocks for your store (or shortcodes like [woocommerce_cart])?

    Third, is this only when the FedEx shipping plugin is active that this console error appears, or does it occur even with it deactivated?

    Fourth, is this preventing the payment option from loading at checkout? or is this error only something you’ve noticed in admin? If so, could you share some replication steps so that we can be sure we’re focusing on the same problem?

    All the best,
    Amber ??

    I just encountered this issue with 1.7.0. I know it is the GD Payment Gateway plugin because the error went away when I deactivated it. Worried that we’ve lost some event ticket sales, and have yet to confirm.

    Rolled back to 1.6.2 and error is gone.

    This is a crucial component of your customers’ online businesses and channels. I hope you can fix it and release a WELL TESTED fix for 1.7.1.

    Thread Starter Daniel Chase

    (@riseofweb)

    1) Every time the checkout page is visited, the wc-poynt-checkout-block notice appears in the error log.
    2) I do not use checkout blocks. My pages use the standard shortcodes (like [woocommerce_cart]).
    3) If the FedEx plugin is disabled, that error goes away. See my posts above for more details.
    4) This does not prevent the payment option from showing. Note that I do not use the pay-in-person option, nor have it enabled. If you are referring to the pay-in-person option not showing, I have no idea because I don’t use it.

    Plugin Support amberskyverge

    (@amberskyverge)

    Hey,

    Thank you so much for answering the questions, I sincerely appreciate it. I have passed this information along to my team and I will reach back out once I hear back.

    All the best,

    Amber ??

Viewing 15 replies - 1 through 15 (of 23 total)
  • The topic ‘Ver 1.7.0 Issues’ is closed to new replies.