Ryan Ray

Hi @besmannmachine,

This might be something to check with your host with at first. I’m not sure what route to take based on what we know here so far. Also, updating to WooCommerce 3.5.2 or 3.5.3 should help fix some database issues for multisite setups.

Would you be on one of those versions at this time and still seeing this issue?

Hi @ajayghaghretiya1,

This kind of problem is usually caused by either a conflict with your theme or with another plugin.
 
The best way to determine this is to:
 

• Temporarily switch your theme to Storefront
• Disable all plugins except for WooCommerce
• Repeat the action that is causing the problem

If you’re not seeing the same problem after completing the conflict test, then you know the problem was with the plugins and/or theme you deactivated. To figure out which plugin is causing the problem, reactivate your other plugins one by one, testing after each, until you find the one causing conflict. You can find a more detailed explanation on how to do a conflict test here.

Hi @007bmorris,

Sometimes, not all of the time, the shipping address changes on PayPal’s end. Contacted PayPal, they said it wasn’t their problem.

Link to image: http://cld.wthms.co/DCIEDq

The way this can happen is that in your PayPal Standard settings you’ve left this disabled, which is recommended, and then the customer changed their address on PayPal’s site during the checkout process. If they do change their address there is unfortunately nothing we can do to get that change back over to WooCommerce. PayPal just doesn’t offer a way to do that yet.

You can enable this though and it won’t let your customers change the address they entered on your site once they get to PayPal’s site to pick their payment method.

Hi @costelpalote,

Would you be able to send over your system status here as well? We’d mostly be curious to see if you were using a Facebook extension for this or perhaps have another setup to get your products over to Facebook.

You can find your system status via WooCommerce > Status.
Select “Get system report” and then “Copy for support”.  Once you’ve done that, paste it here in your response. Thanks!

Hi @whatswrong,

Sorry about any trouble or confusion here. Just to confirm at first that in your WooCommerce > Settings > Tax the Automated taxes setting is set to Enabled?

Link to image: http://cld.wthms.co/pnoLcL

If that’s enabled then it’s likely there is some confusion around the tax laws for the U.S., assuming your store is based in the U.S. 🙂

At the moment sales tax is normally only charged for the location where you have “nexus.” Just to confirm this, take your store’s base address and test tax calculations with an order from the same state as your store. If your state charges a sales tax then the automated tax rates should be calculated appropriately only for the state/county/city where your base address is set.

Hopefully that helps!

Hi @quipsta,

I believe what you’re experiencing is a known issue outlined here via the WooCommerce GitHub repo. –> https://github.com/woocommerce/woocommerce/issues/22087

It does have a pull request ready for review and looks like to scheduled to get worked into a 3.5.3 release of WooCommerce.

I hope that info on GitHub helps answer your questions. 🙂

Hi @torch01,

Of course this would be possible and likely in a few different ways, but would you be able to explain a little more about the file that is uploaded?

Should the file that’s uploaded be sent out to ALL users who’ve purchased a specific product?

Hi @cristinacaporali,

Thank you for clarifying exactly what you were referencing. When you’ve mentioned importing products from a CSV file do they contain content for the description to begin with?