sgoerger

I am experiencing the same with latest Elementor update, and the setting that was the workaround is gone. Any way to disable that programmatically or any other fix suggested?

Hey Brett,

I didn’t have a TIC set at the category level – this is set to “using site default”, just as the individual products were before; nothing has been selected on the term editing screen.

Any other thoughts about what might have happened here? It really did seem to kick in right at the turn of the month, which made me think it would be something new in TaxCloud account that maybe they didn’t make you privvy enough to? But if I’m the only one this happened too, maybe that’s a bad guess.

Thanks,

Steve

Second something like this. Even for one picture … a spinner or something would be very useful!

Bump here please – any further thoughts on how to keep orientation from switching sideways?

Any help from developers?

@comemanu – any luck on your end?

In my initial testing I’m having the same issue. Taking image on iphone in portrait orientation, but it’s turned to landscape immediately on site frontend and also in the email attachment. Would be better for me to keep these portrait – I think this is going to be a very typical use case for my users. Thanks!

Hey Brett,

Thanks for your reply. Strange set of he-said she-saids I’m trapped in here! Not meaning to blame you, just feels odd that there’s not a sense of urgency around getting this fixed.

I understand that the SST website SSL cert has been down a while. Since it’s been so long but the plugin errors are new, I guess this is not the SSL that is the issue. (Though it’s crazy that this remains down, hard way to make sales!)

For the second bit … they’ve renewed some certs. They also moved some api services, I believe: see https://status.taxcloud.net/ and the message “We have migrated to an Azure App Service and the redirect to taxcloud.asmx is different. If you are having issues please use asmx.taxcloud.com/1.0/?wsdl asmx,taxcloud.net/1.0/?wsdl”.

I’m sorta guessing that the plugin needs to be updated to point to these new api locations? What do you think?

Thanks for your help.

Bump, any help with this on a Friday to end the week? thanks.

I’m on pro version BTW

I’m seeing this issue on a client site as well. Is there any universal fix? Will there be a patch released to the plugin soon?

Second! Is that forthcoming, good sir Aaron!? Thanks!

not yet, and the problem is back! I will appeal to developers now or maybe they will see it here.