Forum Replies Created
I managed to reproduce in an iOS 12 simulator. This error only happens in iOS 12, so that’s why it started happening just recently for you, turns out it hadn’t anything to do with Sucuri 🙂
I’ve implemented a fix and it will be included in the next release of WooCommerce Services (tentatively, next week). In the meantime, if it’s not too inconvenient, you can use your laptop or any other device that doesn’t have iOS 12.
If you could print labels before using Sucuri, my best guess is that Sucuri is blocking them 🙂
The label PDF is retrieved making a
GETrequest to this URL:
So, you’ll need to configure Sucuri to allow that URL too.
If that’s not the issue, could you please tell us which browser and operating system are you using? It will help us reproduce the error.Forum: Plugins
In reply to: [WooCommerce Shipping & Tax] Remove Tariff Requirement
Our understanding (by reading official documentation) is that the tariff numbers are strongly encouraged, altough not mandatory. Just out of curiosity, you’ve never had any problem with Customs? What countries did you ship to? Probably the US/Canada customs is more lenient than, say, if you shipped to Europe or Australia.
I’m in the middle of implementing this change, but I want to be sure that leaving the tariff number blank won’t cause too many headaches for other merchants 🙂
It’s great to hear that it’s working now! I get that all this can be a bit confusing at first 🙂
The “Packaging Manager” should be used to define the boxes you have to pack items into. If you’re using “Priority Mail Flat Rate”, you don’t need to add anything to the Packaging Manager, since the boxes you are going to use are provided by USPS.
I took a look at your store, and I think the problem may be that the items are too big. You configured them as being “6 x 6 x 1” inches (which seems a bit too big for a guitar strap). So, if you only have configured the Priority Mail Small Flat Rate Box (“5-3/8 in x 8-5/8 in x 1-5/8 in”), there’s no way to fit 2 of your items in the same box. I recommend you try enabling bigger Priority Mail Flat Rate boxes, or you make sure your products have the correct size.
Please let us know if that helps 🙂
Sorry for the delay, this error should be fixed in the plugin version
1.15.1, released earlier today.
Please try to go through the Checkout in an incognito window or a different browser, since it’s possible that existing sessions will still be affected. If the problem is solved on an incognito window, you can remove all your sessions and cart save states going to
WooCommerce -> Status -> Tools -> Clear customer sessions. This will affect customers that are mid-purchase (it will empty their carts), so please be mindful of that.
That’s all you need to know, keep reading for the “fun” technical details 🙂
Wow, this one was hard to track down. I don’t want to get too technical, but we added some emojis (an “envelope” emoji and a “box” emoji) to make it easier for the admin to see which boxes should they pack the order with. On a default WordPress installation, the MySQL database uses
utf8mb4encoding, and that works fine. But when the database encoding is
utf8(as it was the default in older versions of WordPress), trying to store a text with an emoji in it would throw an error. The whole session and cart system uses the database, so that was the problem.
It was so difficult to track because we wouldn’t have thought that the database encoding would have anything to do with this, we all just have the default
utf8mb4encoding in our test sites, and
UTF-8should in theory be enough to store emojis. On the words of another contributor to this plugin, which shall remain anonymous, “that’s probably the weirdest bug I’ve ever seen”.
I could reproduce the issue in your site. But, unfortunately, I couldn’t in my testing site.
Could you please try to remove the
Canada Postshipping service and just use 2 simple shipping services, like “Flat Rate” and “Local Pickup”? If the problem is still present, then the issue is not in WooCommerce Services.
Even if it’s not our fault we’ll keep helping you figure out what the problem is, maybe it’s a bug on WooCommerce and we want to fix those too 🙂
A good first step to track down this bug is to create an Staging site, so you can disable or even uninstall plugins and themes and change your configuration without affecting your real site. You can use the WP Staging plugin for creating an Staging site.
Is the problem that you can see the different shipping options in the checkout page, but you can’t click on them? We haven’t changed anything in that area recently, certainly not between version 1.12.2 and now.
If the problem is that your customers can’t get shipping options at all, USPS is having some major problems since about a week ago. That means that it will intermitently fail to get shipping rates, but that affects all plugin versions, even 1.12.2.
Could you please clarify what problem are you experiencing?
In reply to: [WooCommerce Shipping & Tax] Printing Label is VERY slow
We’ve heard about this kind of problem before. Some hosting providers provide a caching server that can interfere with HTTP requests like the “Purchase Label” request. A few months ago we changed the “Purchase Label” request to use “POST” instead of “GET” so it wouldn’t be cached in the most normal hosting configurations.
What hosting provider are you using? In general, “POST” HTTP requests should never be cached, but maybe your hosting provider has a more aggressive default configuration. The caching server we had problems before is called “Varnish”, maybe you can find its configuration file in your site?
Sorry for the inconvenience, we missed that error in our last update.
We have just released WooCommerce Services version 1.14.1, the only change it has is that it has that bug fixed.
Please tell us if that solved your problem 🙂
Sorry for the late reply, we wanted to include several things in this release.
We’ve just released version 1.12.0 of WooCommerce Services. We fixed the error you’re getting (that’s an error while trying to log an error), so at least now you’ll be able to see what is happening with the plugin. You’ll be able to see any error message in
Hope that helps! Please tell us the error you get if it’s not obvious how to fix it 🙂Forum: Plugins
In reply to: [WooCommerce Shipping & Tax] Doesn’t recognise valid US address
We are using the official USPS address validator to check the addresses. You can check here that the address isn’t valid (according to USPS). If you change the “69” for “67”, for example, the address is valid.
Are you sure the address is valid? I’ve done a quick check on Google Maps and when you search for “69 Sheldon St” it points you to a house, but when you open Street View the address is “5 Sheldon St”.
I’m afraid you won’t be able to purchase a label for that address using our service (or any other online service). USPS simply won’t let any automated system purchase a label for what it considers to be an “invalid” destination. Maybe in this case you’ll have more luck going to the post office and talking with a human 🙂
Thanks for creating the ticket, that should make things easier.
I’m marking this as “Resolved” and continuing to solve this in private.
You can open a ticket following this link: https://woocommerce.com/my-account/create-a-ticket/ then going to the
Free Extensionssection on the sidebar and select the
WooCommerce Services Extensionin the dropdown that says
Select an extension. Then you can create a ticket. See the screenshot:
It is a child theme of mystile. The theme style sheet is default.css and it has custom css in the display options. I don’t know where to find out what it’s name is. On my dashboard it is called mystile-child, is that what you are looking for?
Yes. I was hoping the child theme was publicly available, but instead it’s a custom one. So we can’t help you with that, because we can’t get your theme and try it ourselves. As I recommended a few posts back, could you try to use
mystileinstead of your custom child theme? If it works that way, then the problem is in your custom code. If it still doesn’t work, then the best think you can do is open a ticket so we can look at the rest of your plugin versions to see if we can find any incompatibility that we haven’t found yet.
- This reply was modified 5 years, 2 months ago by danreylop.