bügelfrei

W3TC responded to a bug report I sent and they say that it should be fixed in a future release.

Thanks for responding, @vmarko.

I double-checked my Cloudflare account and re-confirmed that my global key is 52 characters, and then I created a second token just for W3TC and once again got a 53 character token.

So I went into Extension_CloudFlare_Api.php and changed

    if ( 40 === strlen( $this->_key ) ) { // CF API Token.

to

    if ( 53 === strlen( $this->_key ) ) { // CF API Token.

and I was able to authorize Cloudflare. My subsequent tests confirmed that as long as I keep my modification in W3TC’s code, the plugin can purge Cloudflare’s cache for me.

Obviously this is going to break if the plugin is updated and no longer accepts 53 character CF API tokens.

Hi @mosesmedh,

Thanks for jumping in here.

Could you please try clicking on the Shipping tax class setting and change it to “Based on cart items”? After saving the changes, let me know if the tax calculation at checkout updates correctly.

As long as this plugin (WooCommerce Tax) is enabled, the dropdown shows “Standard” and can’t be changed. Curiously, if I disable the plugin and reload the Tax tab in WC’s settings, the dropdown becomes editable and offers all the expected options, including “Based on cart items”. Unfortunately, even after saving the setting as “Based on cart items”, Shipping tax class will revert to standard once WooCommerce Tax is re-enabled.

This is unexpected, right?

I went through a cycle or two of disabling, deleting and reinstalling WooCommerce Tax to see if it made a difference, but it’s still the same. (The delete/reinstall cycle emptied the tax tables, so I assume it was a decent reset for the tax plugin.)

Also, I’d like to confirm whether your shipping methods are set as taxable. How were these shipping methods created, through WooCommerce’s default settings or using a third party shipping plugin?

Confirmed: my Media Mail shipping method (created via WC Settings > Shipping > Shipping zones > zone: “USA”) has Tax status = Taxable.

Additionally, I’m using a plugin (Multi-Carrier Shippo Shipping Rates & Address Validation for WooCommerce) to get other US and all international rates. I tested disabling this plugin just now with no effect on sales tax calculations.

I’m glad if I was able to help you find and fix an issue. Thank you for making the plugin!

I think your test is ambiguous because “post_title” and “ID” are both WP core fields as well as headers in your CSV. Without looking at your plugin’s code, my guess is that the core fields are getting “post_title” and “ID” values from the CSV and then header manipulation for the ACF field is manipulating the values from the WP core fields instead working directly with the values from the CSV.

Here’s a one-line sample from the data I was importing:
https://alexanderbailey.com/bb_use/gigpress-export-for-Ultimate-CSV-XML-Importer.csv

See if you can concatenate the address-related fields into a your ACF “text” field, for example:

{Street}, {City} {State} {Postal code} 

Sorry if I’m being obtuse!

Hi @riswanasmack. Correct, I was using the free version.

It looks like you are using field names (e.g. “post_title”, “post_name”) when you do it in your screen recording rather instead of headers from the CSV.

In my scenario, I was importing a CSV which included “Street”, “City”, “State”, “Postal code”, “Country” headers, which I wanted to concatenate to a single ACF field “Address” when importing. I tried using things like “{Street}, {City} {State} {Postal code}, {Country}” but ended up with nothing in the ACF “Address” field after import.

Maybe I could have made the address concatenation work during import if I had created extra ACF fields for each of the CSV columns and then used the field names for each field? I can see the value creating excess fields for a routine (repeating) import, however, I was just doing a one-time import to migrate data from an old (dead) plugin to an ACF-based solution.

In all fairness, I discovered FluentSMTP (and the trick) by way of this blog post: https://adityaarsharma.com/how-to-use-smtp-email-in-wordpress-multisite-globally/.

Of course, I skipped the network-activate and then network-deactivate steps (by accident, because following directions is not one of my strengths). So, now we know that there’s no need to network activate the plugin at all.

Thanks again!