jessepearson

Hey @thekendog , the Accommodations plugin is an extension of the Bookings plugin, which is a paid plugin. You can get direct support through your account at WooCommerce.com for the Bookings plugin and the Accommodations plugin.

For the customer email, I was only able to replicate this by manually resending the emails from the admin. I’ve created a bug report for the team to look into:
https://github.com/Automattic/woocommerce-payments/issues/3513

I’ve also created an enhancement request to add filters to disable explicit formatting entirely:
https://github.com/Automattic/woocommerce-payments/issues/3514

As for the print out, this will have explicit formatting due to it’s being done from the admin. Once the filters are added, you will be able to use them and disable this.

Thanks for taking the time to report the issue and do further testing ??

@aclancy I am part of the team that works on Multi-Currency within WooCommerce Payments, and this issue has us curious. We set it up so explicit formatting (meaning with the currency code like USD) should show in the admin all the time, but this shouldn’t happen on the front end of the site if Multi-Currency is disabled, or if there’s only one currency enabled in Multi-Currency. I just double checked, and that is the result I had.

The code that decides if explicit formatting should be used is here:
https://github.com/Automattic/woocommerce-payments/blob/3.4.0/includes/class-wc-payments-explicit-price-formatter.php#L53-L94

If you’re still having this issue, we’d like to dig into it further to see what the issue may be. Also, if needed, we can add a couple filters that would allow disabling explicit formatting within WooCommerce Payments entirely.

@daigo75 No problem, and agreed.

Just want to note that there is an option to disable Multi-Currency in the settings. It is under Payments > Settings > Advanced, you then uncheck the box and save the settings.

@kirstensmitcreative The Multi-Currency feature built into WooCommerce Payments is designed only to work with the widget included with it. Can you give some more information on why you’d like to use a different widget?

@kirstensmitcreative Would you mind trying to add additional currencies again and letting us know if you encounter the issue again? The fix I mentioned that was created has been added to the plugin, but it will not be released next week. My team and I tried to replicate the issue, and also looked over the code, and couldn’t find how this happened. The only thing we could think is that some other error happened and the option didn’t update correctly in the database.

@kirstensmitcreative Multi-Currency is built into WooCommerce Payments, but will only work if you have set up an account to accept payments. That specific row in the database specifies the enabled currencies that are found on the page at WooCommerce > Settings > Multi-Currency. If it is empty, then it will be added/updated when new currencies are added to that page.

I am not sure how the row in the database became a string (just text) instead of an array (list), as the code itself always sets the value as an array. Removing the row would have solved the issue, so you should be able to proceed if you’ve set up an account with WooCommerce Payments.

Hey @schmidtig, can you create your own thread and list the error you are getting for us to take a look at? Thank you ??

@gong8451min That particular error happened when the analytics built into WordPress was processing an order. You can go to Analytics > Settings, then scroll to the bottom. Once there, uncheck the Skip previously imported customers and orders box, then click Start to import. The import should finish without any errors.

Hey @w-sky, version 2.8.4 has been released, which fixes the issue with Subscriptions. Please update and let us know if you have any further issues.

@sayeed88 @gong8451min Just wanting to note that WooCommerce Payments has a new version out that should resolve any fatal errors from 2.8.3. Please update to see if that resolves the issues you have seen.

Hey @w-sky !

The issue is caused by WooCommerce Payments being active, but not connected to an account. The next release should have a fix.

For reference, the issue was reported here, which includes a link to the fix:
https://github.com/Automattic/woocommerce-payments/issues/2687

Hey @kirstensmitcreative !

I just looked over the error, and it looks like a string is getting pulled from the database instead of an array. A quick fix would be to go into your options table in the database and delete the row with wcpay_multi_currency_enabled_currencies as the option_name.

The options table is typically wp_options, but if your database prefix is something other than wp_, it may start with something different, but still end in _options.

There is a fix created and in for review at the moment, it can be seen here:
https://github.com/Automattic/woocommerce-payments/pull/2711

@thiagoqf There may be an issue with another one of the plugins that is installed, or there could be a data or database issue somewhere. Tracking down the actual cause may take some time. The steps to take would be:

• Create a copy of the site on the same server to test with. Deactivate all plugins but WooCommerce. Can you replicate the issue? I know you mentioned a moderate level of traffic causes it, but this is the best route.
• Check to see if you have a large number of categories, tags, or product attributes. A large amount of taxonomies or terms can cause database slowdowns.
• Can you copy the site to a local environment or another server to see if the issue persists?

More about conflict troubleshooting can be found here: https://docs.woocommerce.com/document/how-to-test-for-conflicts/