Bernat Torras (a11n)

Hi there,

As you say, the “woocommerce_states” filter is applied to both the billing and shipping states, as they’re all generated from the same function (WC()->countries->get_states( $country )).

Right now, there’s no way to change the shipping states without altering the billing ones or without changing WooCommerce’s core code.

If you think that this would be a good feature to add to our plugin, I’d suggest you to request it in our [suggestions area](http://ideas.woocommerce.com). We’re always interested in ways to make Subscriptions better, and the suggestions area is where you can submit ideas and vote on features you’d like to see added. We implement new features from this list based on popularity, so your input helps us tailor our development efforts to better serve you and all of our users. We greatly appreciate it!

Alternative, you could use a workaround like this to enable the shipping methods only for a specific states. All the states will still appear in the selector, but your customers will only be able to place the order when the specified ones are selected.

You can also add a note to the Checkout page to tell your customers that you only deliver your orders to these states.

I hope it helps!

Hi there!

That is pretty odd, as by default, the WP_Tracker class should be included in WooCommerce and embedded when this file is being executed.

Can you please check if you’re using the latest version of WooCommerce?

Also, can you please try to deactivate and delete it from your Plugins page and install it again? I suspect that your current version of WooCommerce could be a bit corrupted (it could happen if the update or download process breaks) and some files could be missing…

If you download the latest version of the plugin and the issue persists, this will likely be caused by a conflict with your theme or with another plugin.

The best way to determine if the issue is being caused by a theme and/or plugin is to temporarily switch your theme to Storefront (https://woocommerce.com/storefront/?aff=10486&cid=1131038) and disable all plugins except for WooCommerce. Finally, test to see if the issue is resolved by checking if your site is displayed correctly.

To figure out which plugin is causing the problem, continue to the next step – reactivate your other plugins one by one, testing after each, until you find the one causing conflict.

Here’s a more extensive explanation in our docs: https://docs.woocommerce.com/document/how-to-test-for-conflicts/

—–

Tools to help you troubleshoot:

– Meks Quick Plugin Disabler is a plugin you can install which will remember what plugins you currently have active so it’s easy to switch them back on. Link: https://wordpress.org/plugins/meks-quick-plugin-disabler/

– Health Check is a plugin that allows you to temporarily disable other plugins and switch themes for that session without impacting your users. Link: https://wordpress.org/plugins/health-check/

– You can clone your site to a staging environment and perform tests without modifying your live site or impacting customers. Many hosts provide staging facilities, so it’s worth checking in with them. It’s also possible to do it using the free WP Staging plugin. Link: https://wordpress.org/plugins/wp-staging/

Hi there!

That’s pretty odd! I suspect that some other plugin can be generating a compatibility conflict here, causing this unexpected automatic update.

Read more about plugin and theme conflicts in our [Self-Service Guide](https://docs.woocommerce.com/document/woocommerce-self-service-guide/).

This is likely caused by a conflict with your theme or with another plugin.

The best way to determine if the issue is being caused by a theme and/or plugin is to temporarily switch your theme to Storefront (https://woocommerce.com/storefront/?aff=10486&cid=1131038) and disable all plugins except for WooCommerce. Finally, test to see if the issue is resolved by opening an order from the backend again.

To figure out which plugin is causing the problem, continue to the next step – reactivate your other plugins one by one, testing after each, until you find the one causing conflict.

Here’s a more extensive explanation in our docs: https://docs.woocommerce.com/document/how-to-test-for-conflicts/

—–

Tools to help you troubleshoot:

– Meks Quick Plugin Disabler is a plugin you can install which will remember what plugins you currently have active so it’s easy to switch them back on. Link: https://wordpress.org/plugins/meks-quick-plugin-disabler/

– Health Check is a plugin that allows you to temporarily disable other plugins and switch themes for that session without impacting your users. Link: https://wordpress.org/plugins/health-check/

– You can clone your site to a staging environment and perform tests without modifying your live site or impacting customers. Many hosts provide staging facilities, so it’s worth checking in with them. It’s also possible to do it using the free WP Staging plugin. Link: https://wordpress.org/plugins/wp-staging/

Please give it a try and let us know if the issue is related to any of your other active plugins.

Hi there!

I think that you could use a simpler approach using the “woocommerce_email_attachments” filter to add your PDF attachments to the default WooCommerce notification emails.

Here’s a tutorial and a Stackoverflow thread with more details:

– http://www.mbcreation.com/adding-email-attachments-in-woocommerce/
– https://stackoverflow.com/questions/41632921/woocommerce-email-attachment

Also, please mind that there’s an official WooCommerce plugin designed for this same purpose: https://woocommerce.com/products/email-attachments/

I hope it helps!

Hi there!

That’s pretty odd! Especially if it only happens when placing the order with Stripe…

Have you tried to disable all your plugins (except WooCommerce and Stripe) to see if the issue persists? If it’s solved, it means that one of these deactivated plugins was generating a conflict with WooCommerce/Stripe. Enabling them one by one again and repeat the test will help you find the culprit!

Of course, check as well that you’re using the latest version of WooCommerce and Stripe plugins!

Let us know if the issue persists!

Thanks

Hi Jin,

That’s pretty odd and I still suspect that some plugin or customization in your site is generating this conflict, as by default, the “payment_method” parameter shouldn’t be empty.

Can you also try to switch to a default WordPress theme to see if the issue persists? If it’s solved, I’d suggest you to check your theme’s functions.php file as there will be likely some customizations that alter the cart there.

Also, can you please check if you’re using the latest version of WooCommerce and Stripe?

Finally, if the issue persists, I’d suggest you to enable WordPress debug log functionality and check if any errors are logged in wp-content/debug.log file when replicating this issue.

You can read more about how to enable WP_Debug here:
http://codex.wordpress.org/Editing_wp-config.php#Debug

Here are the basic steps:

1. Login to your site through FTP
2. Make a backup of wp-config.php
3. Open this file and add the code below
4. Save and re-upload this file

Find this line of code: define('WP_DEBUG', false);

Change it be this:

// Enable WP_DEBUG mode
define('WP_DEBUG', true);

// Enable Debug logging to the /wp-content/debug.log file
define('WP_DEBUG_LOG', true);

// Disable display of errors and warnings 
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors',0);

Thanks so much!

Hi there,

By default, WooCommerce doesn’t support multicurrency and therefore, it isn’t possible to assign different taxes or shipping methods to products based on these currencies.

As far as I see it, the only way to achieve it would be to create some custom PHP code to apply different shipping methods or taxes to the products based on the current currency.

Another thing that you could check is Multilingualpress plugin. As it works on a multi-site approach, maybe you would be able to specify different product settings (taxes, shipping class, etc) for each site/currency.

I hope it helps!