amrevnc

Thank you for the quick replies. I am aware of the paid services. However, I see no reason to pay for them when I only need to pay taxes in one state, and could easily enable that if Woo provided a County field. Note that taxes also have to be *filed* on a county by county basis (in many states). As of now, I will have to manually determine each customer’s county. With a County field, I could request it from the customer, and report it out of Woo with the rest of the information.

Mtg169, that is very helpful about Jetpack and Tax. Is the same true for Woo Payments, which also claims to require Jetpack?

Thank you,
Jim

Update: At the suggestion of Dreamhost, I deactivated all of the Woo plugins, Jetpack, and W3 Total Cache. I reactivated just WooCommerce, went to options.php, and was able to change the “no” to “yes.” I then reactivated everything else. Now the “/wc-api/v1/” and “v3” tests shows the API is enabled.

However, the original problem remains with the vendor plugin not syncing. I will go back to them for that support.

Thank you for your help.

Apparently only the webhost admins can access that info, *but* you led me to the solution. In talking with Dreamhost support about this, they said the 0755 might have to be set to 0775 for some apps to write to the folder. They did that, and it worked! Thank you very much for your help.

Okay, thanks. It appears to have the perms:

drwxr-xr-x (0755)

Thank you for your help!

I don’t have the skills to know what I’m looking at using your “wp-json/wc/v3” link. I do know the plugin was *not* using the Legacy API when everything was working. (I did not check the Legacy API box until you suggested it.) And when I run “/wc-api/v1/” or “”/wc-api/v1/” it returns the API as disabled.

You made an excellent catch regarding “options.php.” It shows a “no,” and worse, it won’t save the “yes” setting. That is, I enter “yes,” click “Save,” and if I go right back to that line it has reverted to “no.” I tried it twice!

I also tried the String Locator, but the server returned a 400 Bad Request error. I presume that has to do with the server security settings (a shared server on Dreamhost).

Any idea what would prevent me from changing that option?

Best regards,
Jim

Sorry for the multiple posts, but I thought I should share that I experimented with plugins last night without success. Specifically, I:

1. Turned off W3 Total Cache (after purging all caches)
2. Set Cloudflare to bypass its cache (that is, load directly from the site server)
3. One at a time, turned off each plugin not in place the last time the sync worked, and tried the sync
4. De- and reactivated the Printful plugin (the site I am trying to re-sync with)

Also note that earlier I created a new WooCommerce API key and revoked the old one.

After all this, the conditions in my original post remain true.

Apparently I lied. The problem has recurred. I tried revoking the old API key and adding a new on, and that did not fix the issue.

I would be grateful for any help.

I have solved the problem. The answer was unintuitive, so I am adding it here for anyone else who runs into it.

I had made a change in the “functions.php” file of my child theme for an unrelated purpose (a workaround to enable Jetpack to display the social sharing icon for e-mail without using Akismet). Specifically, I added this line at the bottom of the file:

add_filter( ‘sharing_services_email’, ‘__return_true’ );

Removing that line fixed the issue. Don’t ask me why. ??

Thank you for this suggestion. I tried it, and the problem did not resolve.

Sadly, Bruce, it does not work as we expected. Upon deactivating AIOSEO, the meta description seemed to have disappeared from the page source. Upon reactivating it, I realized it still wasn’t in the page source. Apparently AIOSEO serves its metadata out each time the page is called, which explains why it is such a loading-time hog, which is why I wanted to get rid of it.

Thank you anyway,
Jim

That does, thank you, Bruce. I assumed that was the case, but wanted to double-check before taking the plunge!

Best regards,
Jim

Okay, didn’t realize this could be theme-specific. Will do, and thank you!

That is kind of you, Cory. I will do so now.

Thank you,
Jim

Thank you for the quick reply. But the FAQ link you sent is about a problem in the Duplicator UI. My issue is in the WordPress UI post-migration.

I cannot submit a ticket because I was only migrating the one site and did not need Pro features.

Regards,
Jim

Yeah, I was afraid of that: I worked in software long enough to recognize an “edge case” when I’m in one. ??

That’s what I had done, but some of my customizations are in various settings or directly in the PHP, so there’s no easy way to back up and restore them. Nonetheless, I saved my CSS and took a bunch of screen shots before reinstalling Woo. So far, so good.

Thanks again,
Jim