digimarkup

I would also like to add to this. When I edit a page, the Jeg Kit tab turns to blue as if it’s the active tab when it’s not. This is the dumbest form of advertising that I have ever seen in a WordPress plugin. You don’t get people to pay for your membership by pissing them off. What are you guys doing?

This problem still exists, but I’ve found the solution.

In version 9.7, the validate_create_customer_request method was added in includes/class-wc-stripe-customer.php on line 219.

This function retrieves the required fields from the get_create_customer_required_fields method, which gets its data from:
WC_Checkout::instance()->get_checkout_fields( ‘billing’ );

By default, every billing field is required, except for the company and billing_address_2 fields. That includes the phone number field.

So, if the customer leaves out any field (except company and address 2), the checkout will fail. The data won’t even be sent to the Stripe API.

Another issue is that not every WooCommerce order requires a billing address. For example, I run a digital product store and don’t need to collect address information.

In the get_create_customer_required_fields method, there’s a condition that checks if the user is on the “Add Payment Method” page:

// If we are on the add payment method page, we need to check just for the email field.
		if ( $is_add_payment_method_page ) {
			return [
				'email' => true,
			];
		}

This logic also needs to be applied when an admin manually creates an order and sends it to the customer. Manually created orders do not display billing fields during checkout.

There are two ways to fix this:
Use the wc_stripe_create_customer_required_fields filter to override the required fields.

Use the woocommerce_billing_fields filter to customize which fields are required.

https://developer.woocommerce.com/docs/code-snippets/customising-checkout-fields/

The crazy thing is I did not install this plugin. This was installed automatically by WooCommerce. I did not have the legacy rest api activated. Unacceptable from a plugin owned by Automattic

v1.6.21 did not fix this issue. I just updated and the problem still exist.

There’s a bug in the Elementor plugin that causes this. To temporary fix this problem, you will need to edit a javascript file. The file is located here

wp-content -> plugins -> elementor -> assets -> js -> app.min.js

Copy this file content and paste it into a code editor like vscode or notepad++

Find this line and remove it

a[a.length-1].remove()

Only remove this line and nothing else. Copy the code and paste it back into the app.min.js file, overwriting the code that’s already there. Save the file and try using the import tool again.

Unless Elementor fixes this bug, the problem will return when a new update is released.

• This reply was modified 2 years, 12 months ago by digimarkup.