ifnoob

Sorry. It turns out that this issue is not a Stripe issue, but is caused by other plugins.

WooCommerce > Status > Logs -> there is no.

Apple pay is unconfirmed. Google Pay screen From the staging site
https://imgur.com/a/8WgBTqY

For example, €10.00, not €10 <- No €1,000

All contents of the system report are not allowed for security reasons.

Of course, this has been checked and the amount at the time of purchase is normal.
The display adds 00.
On a real-time site, testing with different settings would pose a big risk of problems, as purchases are made frequently.
The same symptom also occurs on staging sites.

https://imgur.com/3LIFO0r

This is a screenshot from the client side.
It shows 2,970 yen <- 297,000 yen.

• This reply was modified 1 week, 6 days ago by ifnoob.

I wasn’t able to take a screenshot, but I’m having the same issue as ZIPANG.
The price displayed is 275,000 yen, but the purchase price is the normal 27,500 yen.

確認後正常な稼働になりました。
早急な対応ありがとう御座いました。

According to the image in the WooCommerce status, after Stripe payment is completed, I always get a final-errors.
I looked into this as well, but the cause is unknown, so I just wanted to let you know that this has happened.

Thank you for your response. I will consider this matter resolved.

Does the issue occurs also when using other editors in the CRM, for example invoices?

I’m still new to Jetpack CRM, but I can’t find MCE on my invoice.

Have you tested the editor with a different theme to see if the issue persists or if it’s purely a theme conflict? What’s the theme you’re using at the moment?

theme has been confirmed on Blue Note and Storefront.

Does the decimal in the Yen currence affect the way you enter the amount of money? In other words: would removing the decimals make an improvement in the way you use the quote feature?

WooCommerce already supports decimal points in amounts, so I want to avoid visual mistakes.

CSS included .dropdown-menu is common and conflicts with themes.

OceanWP has a CSS class conflict with .dropdown-menu.
Suggestion .zbc-dropdown-menu

Plugins other than those mentioned above
Query Monitor
WP Multibyte Patch (Japanese environment only)
Redis Object Cache

No, the same symptoms occur in the WooCommerce plain environment, and [Shortcode] solved it, but when selecting a category with a widget, it will not be in the new order of parameters, which is inconvenient. I will contact the developer Github.
thank you.

class.swpm-utils.php on line 424
$_POST[‘membership_level’]
where is this field from?

All set Enable Free Membership or Free Membership Level ID
login or new registration error

Environment
httpd : LiteSpeed
PHP: 7.4.33
SQL: mysqlnd 7.4
Simple Membership + Simple Membership After Login Redirection + Simple Membership Form Builder

Sorry.
Since then, when I tested it with plain WooCommerce, there was no Final Error.
It may be conflicting with other plugins and I don’t think there is a problem on your side.

Partial contents of the staging server

### WordPress Environment ###

WordPress address (URL): https://
Site address (URL): https://
WC Version: 7.0.1
REST API Version: ? 7.0.1
WC Blocks Version: ? 8.5.2
Action Scheduler Version: ? 3.4.0
Log Directory Writable: ?
WP Version: 6.1
WP Multisite: –
WP Memory Limit: 1 GB
WP Debug Mode: ?
WP Cron: –
Language: ja
External object cache: –

### Server Environment ###

Server Info: Apache
PHP Version: 8.0.16
PHP Post Max Size: 1 GB
PHP Time Limit: 180
PHP Max Input Vars: 1000
cURL Version: 7.29.0
NSS/3.53.1

SUHOSIN Installed: –
MySQL Version: 10.5.13-MariaDB-log
Max Upload Size: 1 GB
Default Timezone is UTC: ?
fsockopen/cURL: ?
SoapClient: ?
DOMDocument: ?
GZip: ?
Multibyte String: ?
Remote Post: ?
Remote Get: ?

### Database ###

WC Database Version: 7.0.1
WC Database Prefix: wp_
データベースの合計サイズ: 18.79MB
データベースのデータサイズ: 15.64MB
データベースのインデックスサイズ: 3.15MB
wp_woocommerce_sessions: データ :0.02MB + インデックス :0.02MB + エンジン InnoDB
wp_woocommerce_api_keys: データ :0.02MB + インデックス :0.03MB + エンジン InnoDB
wp_woocommerce_attribute_taxonomies: データ :0.02MB + インデックス :0.02MB + エンジン InnoDB
wp_woocommerce_downloadable_product_permissions: データ :0.02MB + インデックス :0.06MB + エンジン InnoDB
wp_woocommerce_order_items: データ :0.02MB + インデックス :0.02MB + エンジン InnoDB
wp_woocommerce_order_itemmeta: データ :0.06MB + インデックス :0.03MB + エンジン InnoDB
wp_woocommerce_tax_rates: データ :0.02MB + インデックス :0.06MB + エンジン InnoDB
wp_woocommerce_tax_rate_locations: データ :0.02MB + インデックス :0.03MB + エンジン InnoDB
wp_woocommerce_shipping_zones: データ :0.02MB + インデックス :0.00MB + エンジン InnoDB
wp_woocommerce_shipping_zone_locations: データ :0.02MB + インデックス :0.03MB + エンジン InnoDB
wp_woocommerce_shipping_zone_methods: データ :0.02MB + インデックス :0.00MB + エンジン InnoDB
wp_woocommerce_payment_tokens: データ :0.02MB + インデックス :0.02MB + エンジン InnoDB
wp_woocommerce_payment_tokenmeta: データ :0.02MB + インデックス :0.03MB + エンジン InnoDB
wp_woocommerce_log: データ :0.02MB + インデックス :0.02MB + エンジン InnoDB
wp_acfw_store_credits: データ :0.02MB + インデックス :0.00MB + エンジン InnoDB
wp_actionscheduler_actions: データ :0.05MB + インデックス :0.13MB + エンジン InnoDB
wp_actionscheduler_claims: データ :0.02MB + インデックス :0.02MB + エンジン InnoDB
wp_actionscheduler_groups: データ :0.02MB + インデックス :0.02MB + エンジン InnoDB
wp_actionscheduler_logs: データ :0.05MB + インデックス :0.03MB + エンジン InnoDB
wp_admin_columns: データ :0.02MB + インデックス :0.02MB + エンジン InnoDB
wp_apcm_details: データ :0.08MB + インデックス :0.00MB + エンジン InnoDB
wp_apcm_statistics: データ :0.08MB + インデックス :0.00MB + エンジン InnoDB
wp_commentmeta: データ :0.02MB + インデックス :0.03MB + エンジン InnoDB
wp_comments: データ :0.02MB + インデックス :0.09MB + エンジン InnoDB

is WooCommerce 7.0.1

PopupData.php

public function get_popups(): array {
		return [
			$this->get_popup_data_step_1(),
			$this->get_popup_data_step_2(),
			$this->get_popup_data_step_3(),
//			$this->get_popup_data_step_4(),
		];
	}

In emergency processing Operate with this.