Paulo P - a11n

Hello,

Thanks for writing back and sharing the additional details.

I can confirm that, by default, users with the “Editor” role can access the MailPoet > Emails section freely. But let me clarify with the team if having access to the “Status” (and thus the email addresses) is intended as well.

Best,

Thank you! We really appreciate you for taking the time to leave us a positive review.

Hello,

After discussing this with the developer team, they asked that the conversation is taken to the GitHub repository where development takes place. I see that someone else from the community has already created an entry for this very issue:

https://github.com/Automattic/woocommerce-services/issues/2697

I’ll add this topic there as a reference and I welcome any other merchants experiencing the same issue to add their voice to the conversation there. You can follow the progress with a free GitHub account and also add any additional details there.

Thanks for bringing it to our attention.

Hello,

After discussing this with the developer team, they asked that the conversation is taken to the GitHub repository where development takes place. I see that someone else from the community has already created an entry for this very issue:

https://github.com/Automattic/woocommerce-services/issues/2697

I’ll add this topic there as a reference and I welcome any other merchants experiencing the same issue to add their voice to the conversation there. You can follow the progress with a free GitHub account and also add any additional details there.

Thanks for bringing it to our attention.

Hello,

There are a number of people reporting the same issue, there’s got to be something going on.

I agree that something has changed in the WooCommerce Shipping & Tax plugin and a clarification is definitely warranted at the very least. After discussing this with the developer team, they asked that the conversation is taken to the GitHub repository where development takes place. I see that someone else from the community has already created an entry for this very issue:

https://github.com/Automattic/woocommerce-services/issues/2697

I’ll add this topic there as a reference and I welcome any other merchants experiencing the same issue to add their voice to the conversation there. You can follow the progress with a free GitHub account and also add any additional details there.

Thanks for bringing it to our attention.

Hey @darkearth10,

Thanks for sharing the additional details. We’re still investigating why this error started showing up just now, but, according to USPS, letters and flats must contain only documents and cannot contain any other goods. Here you can also see that no merchandise may be mailed with FCMI.

I understand that you’ve been using First Class Mail International labels bought via the WooCommerce Shipping & Tax plugin to ship merchandise for a while now, but is not allowed by USPS.

You mentioned that you now have to go to the post office to ship international orders. Are the workers there not raising any issues with shipping merchandise with FCMI?

@grapegrapegrape, I already replied to the other comment you left. Note that this is @darkearth10’s topic, please open your own support topic if you need assistance. We’re happy to look into it!

Hello,

The issue is, that the plugin has its own GTIN field which must be filled in, because it won’t see the GTIN field in Woocommerce. How can this be?

WooCommerce core does not have a GTIN field, only SKU, so I imagine that something else on your site is adding a custom field for GTIN. Google Listings & Ads would need to be made aware of that custom field if you want to use it, as exemplified here: https://woocommerce.com/document/google-listings-and-ads/attribute-mapping-use-cases/#section-4

Best,

Hello,

Yes, I’ve of course tried that and it works as expected with caching disabled.

Great, thanks for confirming. In that case, I recommend that you test a different caching tool (WP Super Cache, for example) and see if you get a different result.

Hello,

I recommend temporarily disabling any caching, so you can test if the WooPayments currency switching feature is working as expected on your site.

Here’s the relevant documentation for reference: https://woocommerce.com/document/woopayments/currencies/multi-currency-setup/

Let us know what you find.

Hello,

Configuring your caching plugin as outlined in the WooCommerce guide linked below should be enough for WooPayments to work correctly:

https://woocommerce.com/document/configuring-caching-plugins/

Make sure your setup is following that guide and let us know if the issue persists.

Best,

Hello,

Thanks for sharing your thoughts on the WooCommerce Shipping & Tax plugin. To clarify, the ability to offer live USPS rates in the cart and checkout pages was a feature offered temporarily between the launch of what was then the WooCommerce Services plugin and the release of WooCommerce 3.5 back in October 2018.

It should be noted that the feature is still available for all the stores that enabled the plugin back then.

Having said that, we are currently exploring future improvements to this plugin and will take your feedback under advisement.

Please let us know if you have any further questions.

Best,

Hello @amgill,

I replied to your ticket in WooCommerce.com a few weeks ago. ?? I wanted to confirm that this code snippet is still working as expected. I created a brand-new test site just now and the custom fields I created were moved over to ShipStation.com perfectly.

For your reference, I created fields with the Checkout Field Editor, replaced “_meta_key” and “_meta_key_2” in the snippet with the field names I created, and injected the snippet using the Code Snippets plugin.

It should work. If it doesn’t, then it is most likely something else on the site causing the issue as my colleagues mentioned earlier, so it might make sense to hire someone to look into it.

Hope this helps!

• This reply was modified 1 year, 5 months ago by Paulo P - a11n. Reason: typo

Hi @odingalt,

That is an automatic reply from our AI Support Assistant. At the end of the message it is asking you to write back if the answer isn’t helpful. So, please just reply to it and someone from our support team will check the ticket.

Thanks!

Thanks for confirming @odingalt! Please contact us at WooCommerce.com > My Account > Support, so we can investigate further. You may need to create an account before you can access that page.

Please include a link to this forum thread, so that we can keep track of what’s already been done.

We will be able to help you further there.

Hello @tristanmason,

At a first glance the developer team agreed that this might be a bug, so I opened up a bug report for further investigation.

At this point we don’t have an estimated time for the fix’s release, so I recommend checking the changelog when a new version gets released to confirm if this has been addressed.

In the meantime, the solution presented on your other topic sounds like a good workaround.

Thanks for bringing this to our attention.