Closed csmcneill closed 2 years ago
5432676-zen
Following plugins were found common
Looks like coming from SiteGround Optimizer
5432486-zen
Can confirm this issue without wp-fusion or siteground. I am unable to login to wp-admin and this same error showed up in the logs.
If i'd have to make a wild guess i'd look at https://github.com/woocommerce/woocommerce-gateway-stripe/commit/c1fc945489db06be9925166269591d05ff2b9adf#diff-e1e5e9b442c2b5d4105edbdc3787651333c1923dd623677025f72d25796900d6R664
@Wqrld I guess 5432486-zen is without WP fusion or Siteground. In fact, they are using WooCommerce Checkout Field Editor, which triggered the error.
Fixed it by adding $this->get_main_stripe_gateway(); to line 662 in woocommerce-gateway-stripe.php as suggested in the code comment for the stripe_gateway() function declaration, probably should have been there to begin with?
54 /* 655 Move the email field to the top of the Checkout page. 656 657 @param array $fields WooCommerce checkout fields. 658 659 @return array WooCommerce checkout fields. 660 */ 661 public function checkout_update_email_field_priority( $fields ) { 662 $this->get_main_stripe_gateway(); 663 $is_link_enabled = in_array( 664 WC_Stripe_UPE_Payment_Method_Link::STRIPE_ID, 665 $this->stripe_gateway->get_upe_enabled_payment_method_ids(), 666 true 667 ); 668 669 if ( $is_link_enabled ) { 670 // Update the field priority. 671 $fields['billing_email']['priority'] = 1; 672
hi all i am still having the same issues i switch off those plugins:
can someone help pleases!
i find the problem which Payment Plugins for Stripe WooCommerce Version 3.3.24
@ABAbdulelah Apply my change from patch https://github.com/woocommerce/woocommerce-gateway-stripe/pull/2397/commits/0741b991fbe018728954bc364a004d5c8486a0bf That should fix the issue until an official update comes out.
25173907-hc
I applied this hotfix that worked for me until bug is resolved. @Wqrld has an even simpler fix posted above.
Problem appears to be that stripe_gateway
can be null.
Is the purpose for the triggering method to move the email field to the top of the checkout page? Curious why that would be needed, especially with so many users who customize their checkout pages?
It didn't seem apparent that this is a plugin conflict bug. It looked like this method was introduced in the most recent version and maybe not fully Q/A'd?
if ( ! is_null( $this->stripe_gateway ) ) { $is_link_enabled = in_array( WC_Stripe_UPE_Payment_Method_Link::STRIPE_ID, $this->stripe_gateway->get_upe_enabled_payment_method_ids(), true ); }
Another report in 5433708-zen
We are experiencing the same issue, the only plugin we have in common with the rest that have commented is Yoast SEO 19.4.
I'm one of the developers here at WooCommerce and wanted to pop in and apologize for the rough rollout on this one. We have people including myself looking into these issues and working on a fix. Unfortunately, it may be a bit slower given the weekend but we're working to get a patch release out for this ASAP.
thanks for the answer. be aware that releasing such version is freezing entirely our business and this should never happen. we are waiting for this fix to earn money and this will as well affect credibility for our customers. I lost as well réservations today because the customers were not able to finalize the order. this is really affecting our business and break the vision customers or prospects may have from us. this has strong consequences while some poeple are enjoying their weekend ! -------- Message d'origine --------De : Lauren Smith @.> Date : 30/07/2022 23:35 (GMT+01:00) À : woocommerce/woocommerce-gateway-stripe @.> Cc : Subscribed @.***> Objet : Re: [woocommerce/woocommerce-gateway-stripe] [6.5.0] Fatal Errors Related to get_upe_enabled_payment_method_ids() (Issue #2394) I'm one of the developers here at WooCommerce and wanted to pop in and apologize for the rough rollout on this one. We have people including myself looking into these issues and working on a fix. Unfortunately, it may be a bit slower given the weekend but we're working to get a patch release out for this ASAP.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
Noting here that 5436225-zen is getting similar error with Stripe + Follow Up Emails + a plugin called Hev Modifiers. In this case a fatal error was logged when a FUE did not send at its scheduled time, nor did any action occur when trying to manually send it
Here's the error log with URL redacted:
2022-07-30T15:20:43+00:00 CRITICAL Uncaught Error: Call to a member function get_upe_enabled_payment_method_ids() on null in /www/dev2apsf_688/public/wp-content/plugins/woocommerce-gateway-stripe/woocommerce-gateway-stripe.php:664
Stack trace:
#0 /www/[SITEURL]/public/wp-includes/class-wp-hook.php(307): WC_Stripe->checkout_update_email_field_priority(Array)
#1 /www/[SITEURL]/public/wp-includes/plugin.php(191): WP_Hook->apply_filters(Array, Array)
#2 /www/[SITEURL]/public/wp-content/plugins/hev-modifiers/hev-modifiers.php(255): apply_filters('woocommerce_bil...', NULL)
#3 /www/[SITEURL]/public/wp-includes/class-wp-hook.php(307): fue_register_variable_replacements(Object(FUE_Sending_Email_Variables), Array, Object(FUE_Email), Object(FUE_Sending_Queue_Item))
#4 /www/[SITEURL]/public/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array)
#5 /www/[SITEURL]/public/wp-includes/plugin.php(476): WP_Hook->do_action(Array)
#6 /www/[SITEURL]/public/wp-content/plugins/woocommerce-follow-up-emails/includes/sending/class-fue-sending-mailer.php(959): do_action('fue_before_vari...', Object(FUE_Sending_Email_Variables), Array, Object(FUE_Email), Object(FUE_Sending_Queue_Item))
#7 /www/[SITEURL]/public/wp-content/plugins/woocommerce-follow-up-emails/includes/sending/class-fue-sending-mailer.php(211): FUE_Sending_Mailer->process_variable_replacements(Array)
#8 /www/[SITEURL]/public/wp-content/plugins/woocommerce-follow-up-emails/includes/sending/class-fue-sending-scheduler.php(58): FUE_Sending_Mailer->send_queue_item(Object(FUE_Sending_Queue_Item))
#9 /www/[SITEURL]/public/wp-includes/class-wp-hook.php(307): FUE_Sending_Scheduler::send_scheduled_emails(2353)
#10 /www/[SITEURL]/public/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array)
#11 /www/[SITEURL]8/public/wp-includes/plugin.php(524): WP_Hook->do_action(Array)
#12 /www/[SITEURL]8/public/wp-content/plugins/woocommerce/packages/action-scheduler/classes/actions/ActionScheduler_Action.php(22): do_action_ref_array('sfn_followup_em...', Array)
#13 /www/[SITEURL]/public/wp-content/plugins/woocommerce/packages/action-scheduler/classes/abstracts/ActionScheduler_Abstract_QueueRunner.php(65): ActionScheduler_Action->execute()
#14 /www/[SITEURL]/public/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_QueueRunner.php(162): ActionScheduler_Abstract_QueueRunner->process_action(82194, 'Async Request')
#15 /www/[SITEURL]/public/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_QueueRunner.php(132): ActionScheduler_QueueRunner->do_batch(100, 'Async Request')
#16 /www/[SITEURL]/public/wp-includes/class-wp-hook.php(307): ActionScheduler_QueueRunner->run('Async Request')
#17 /www/[SITEURL]/public/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array)
#18 /www/[SITEURL]/public/wp-includes/plugin.php(476): WP_Hook->do_action(Array)
#19 /www/[SITEURL]/public/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_AsyncRequest_QueueRunner.php(52): do_action('action_schedule...', 'Async Request')
#20 /www/[SITEURL]/public/wp-content/plugins/woocommerce/includes/libraries/wp-async-request.php(147): ActionScheduler_AsyncRequest_QueueRunner->handle()
#21 /www/[SITEURL]/public/wp-includes/class-wp-hook.php(307): WP_Async_Request->maybe_handle('')
#22 /www/[SITEURL]/public/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array)
#23 /www/[SITEURL]/public/wp-includes/plugin.php(476): WP_Hook->do_action(Array)
#24 /www/[SITEURL]/public/wp-admin/admin-ajax.php(187): do_action('wp_ajax_as_asyn...')
#25 {main}
thrown in /www/[SITEURL]/public/wp-content/plugins/woocommerce-gateway-stripe/woocommerce-gateway-stripe.php on line 664
Getting the same issue when my existing checkout page is queried by GatsbyJS (not a real blocked for me). Comes from this code:
public function checkout_update_email_field_priority( $fields ) {
$is_link_enabled = in_array(
WC_Stripe_UPE_Payment_Method_Link::STRIPE_ID,
$this->stripe_gateway->get_upe_enabled_payment_method_ids(),
true
);
where $this->stripe_gateway
is null.
I also use WC Checkout Field Editor and WC One Page Checkout.
Stack trace if it may help:
{
"errors": [
{
"debugMessage": "Call to a member function get_upe_enabled_payment_method_ids() on null",
"message": "Internal server error",
"extensions": {
"category": "internal"
},
"locations": [
{
"line": 4,
"column": 7
}
],
"path": ["pages", "nodes", 0, "content"],
"trace": [
{
"file": ".../public_html/wp-includes/class-wp-hook.php",
"line": 309,
"call": "WC_Stripe::checkout_update_email_field_priority(array(3))"
},
{
"file": ".../public_html/wp-includes/plugin.php",
"line": 191,
"call": "WP_Hook::apply_filters(array(3), array(2))"
},
{
"file": ".../public_html/wp-content/plugins/woocommerce/includes/class-wc-countries.php",
"line": 1616,
"function": "apply_filters('woocommerce_billing_fields', array(9), 'US')"
},
{
"file": ".../public_html/wp-content/plugins/woocommerce/includes/class-wc-checkout.php",
"line": 228,
"call": "WC_Countries::get_address_fields('US', 'billing_')"
},
{
"file": ".../public_html/wp-content/themes/.../woocommerce/checkout/form-checkout.php",
"line": 43,
"call": "WC_Checkout::get_checkout_fields()"
},
{
"file": ".../public_html/wp-content/plugins/woocommerce/includes/wc-core-functions.php",
"line": 345,
"function": "include('.../public_html/wp-content/themes/.../woocommerce/checkout/form-checkout.php')"
},
{
"file": ".../public_html/wp-content/plugins/woocommerce-one-page-checkout/woocommerce-one-page-checkout.php",
"line": 1597,
"function": "wc_get_template('checkout/form-checkout.php', array(1))"
},
{
"file": ".../public_html/wp-content/plugins/woocommerce/includes/class-wc-shortcodes.php",
"line": 72,
"call": "PP_One_Page_Checkout::one_page_checkout_shortcode(array(2))"
},
{
"file": ".../public_html/wp-content/plugins/woocommerce-one-page-checkout/woocommerce-one-page-checkout.php",
"line": 1542,
"call": "WC_Shortcodes::shortcode_wrapper('PP_One_Page_Checkout::one_page_checkout_shortcode', array(2), array(3))"
},
{
"file": ".../public_html/wp-includes/shortcodes.php",
"line": 356,
"call": "PP_One_Page_Checkout::get_one_page_checkout(array(2), (empty string), 'woocommerce_one_page_checkout')"
}
]
}
]
}
Another report in 5435017-zen.
5440323-zen
5439693-zen
Another report on forum: https://wordpress.org/support/topic/fatal-error-when-i-try-to-generate-invoice/
5440450-zen
5441178-zen
None of the referenced plugins are installed, but the merchant does have both WooCommerce Stripe and Payment Plugins for Stripe WooCommerce: by Payment Plugins support@paymentplugins.com – 3.3.24
36280094-hc
33949676-hc
36283762-hc
11197616-hc
5442429-zen 5442177-zen
It was reported here at 5446363-zen - Asking the merchant to update to 6.5.1
Describe the bug After updating to Stripe 6.5.0, a user in 36234977-hc reported an issue that specifically affected some other extensions, like WP Fusion.
Some elements of other extensions were inaccessible unless they reverted to 6.4.3. Some of this was due to odd styling errors, but others were replaced with the following fatal error:
Note: Redacted their site URL since this is a public repo.
Expected behavior While the onus isn't on the Stripe development team to ensure compatibility with WP Fusion, I wanted to mention this here just in case it is something that should be considered for future releases.
Screenshots
Environment (please complete the following information): SSR: