siwhyatt

Glad you found the root of the issue @wearabletattoo – hope you can get a timely solution!

@wearabletattoo it could also be another plugin that works with WooCommerce that might not trigger when WC is deactivated.

To be sure it would be worthwhile deactivating all the other plugins except WC then see if you still get the error?

A couple of points here @xue28

1. Everything you say about versions makes no sense here as this was not any kind of error, it’s simply how the plugin is designed (badly).

2. The issue was “marked as resolved”, but nothing was ever actually done by Stripe.

@cheechee1 I “solved” this by simply deactivating the saved cards option in the Stripe plugin.

At the end of the day everyone can save their card details in the browser and/or use Google/Apple pay so it’s not really necessary anyway.

I never had any comments or complaints after removing it.

Hope that helps!

Thanks for your reply.

It appears to be some woocommerce functions that I added via the theme file editor that are causing the issue.

To clarify, the website works fine, customers can place orders, and the functions work as intended.

I can also add new posts and pages.

The only issue is when I try to edit an existing page or post.

I appreciate that it is probably out of the scope of this forum to ask for advice on functions, but I thought perhaps you could advise me whether there is an error in the code I have written, or if there is some other issue going on which is out of my control? I’m not sure why, even if my code is suboptimal, it should cause a WordPress critical error when trying to edit a page or post, even when that page or post has nothing to do with woocommerce?

The code which causes the problem is the following:

//Remove add to cart on Christmas conflicts

function hwn_is_purchasable($product_purchasable,$product) {
	
    $xmas_category = 'Christmas';
	
	$array_xmas_incompatible = array(2201, 2202, 2370, 98, 101, 185, 182, 104, 1483, 226, 2377, 718, 88, 2193, 172, 175, 200, 105, 184, 112, 202, 186, 183, 120, 2187, 216, 92, 214);
	
// Return true if cart empty
    if (!WC()->cart->get_cart_contents_count() == 0) {
		
		if (has_term($xmas_category, 'product_cat', $product_id)) {
			foreach (WC()->cart->get_cart() as $cart_item_key => $cart_item) {

				$product = $cart_item['data'];

				if (has_term($array_xmas_incompatible, 'product_cat', $product->id)) {
					return false;
				}
			}	
			return $product_purchasable;
			
		} else {
			if (has_term($array_xmas_incompatible, 'product_cat', $product_id)) {
				foreach (WC()->cart->get_cart() as $cart_item_key => $cart_item) {

					$product = $cart_item['data'];

					if (has_term($xmas_category, 'product_cat', $product->id)) {
						return false;
					}
				}	
				return $product_purchasable;
				
			} else {
				return $product_purchasable;
			}
		}

    }
    // Otherwise, return true.
    return $product_purchasable;
}
add_filter('woocommerce_is_purchasable', 'hwn_is_purchasable',10,2);

//Display message when unavailable

add_action( 'woocommerce_before_single_product_summary', 'unavailable_product_display_message', 20 );
function unavailable_product_display_message() {
    global $product;

    if(! $product->is_purchasable() ){
       echo '<p style="color:#e00000;">' . __("This product is not compatible with items already in your basket. Not all products are available for Christmas delivery. If you wish to purchase offal, nose to tail, chickens or bones or fats please place a separate order. If you wish to order bacon or gammon for Christmas, please use the Christmas Bacon and Gammon products in the Christmas category. Thank you") . '</p>';
    }
}

Thanks,

Simon

Thanks. Actually, I think I prefer the shortcode format in general.

One question – is it possible to hide the short description from the display?

Thanks,

Simon

Thanks Beatrice, much appreciated.

Have a great weekend!

Simon

Hi Beatrice,

I managed to identify the conflict. It’s ARMember Membership Plugin: https://www.armemberplugin.com/

Not sure how or why it’s causing the issue or if it can be resolved?

The website is runnign Astra theme. No captacha plugins.

Works fine on other devices and browsers (including Brave on Android).

It’s just Chome on Desktop.

I can give admin access if you like?

When I have a second I can also test on another install.

Thanks,

Simon

As per the original ticket, I reached out to them already. Ideally, I’d like the details copied across to the new account. Can’t get any action on it though hence looking for alternatively solution.

I understand that the card details aren’t saved – if they were there wouldn’t be a problem!

What are saved are the tokens, and as the tokens don’t correspond to the new account, this is what generates the error.

To be more precise, I want to delete the stored tokens from the woocommerce database to avoid the error.

Can this be done?

Hi Joseph,

Thanks for your reply. Unfortunately, none of these options work for me.

I don’t want to disable saved cards, it’s a very useful function when it works.

I’d like customers to be able to start saving their card details again within the new stripe account.

I can’t really expect all customers to delete all their own cards, and anyway, the issue is the customers don’t know that the saved cards don’t work.

For now I’ve created a modal pop up that appears at the checkout explaining the situation but it seems not all customers see it/understand it, and so continue to try and use the save cards only to get an error message that frustrates them.

What I really need to do is wipe all the existing saved card details so customers can start saving them again.

Is this possible?

Sorry, I just realised I replied to the email that was no reply!

I received 1 of the 2 testimonials. I presume the one from IPhone which works and not the one from Android which isn’t working.

Can this issue be resolved? It’s frustrating for people that attempt on mobile as they take the time to write the testimonial and then it’s lost.

Thanks.

I’ve been having a similar problem.

A bit of troubleshooting has revealed that the problem occurs when someone attempts to submit the form via mobile.

I.e. the form works perfectly on desktop but does not work on mobile.

Is this a known bug?

That worked, thanks!

Thanks. I’ve created a thread and completed the form.

Much appreciated.

I am having the exact same issue.