boxhamster

Thank you for your elaborate answer.
My time zone is correct for where I live, do business etc. Berlin.
I’m on version 9.5.1 of Woo and 6.7.1 of WP.

I just cleared the Analytics Cache, but when trying to “Import historical data” I have an issue. It’s greyed out and says: “Status: Nothing To Import”.

Thanks ??

Hi,
The issue is still present for me.

Thank you for offering your help.
This website: https://swingdancehome.com/en/

Thank you.
However, I’m still seeing the issue on https://citationstyler.com/en/knowledge/literature-research-and-citing-correctly-with-deutsche-zitierweise/?LSCWP_CTRL=before_optm

I’ve turned off Clouflare, refresh all caches, as you see in above link that’s the link without cache also, I’ve made an edit on the Brizy page and saved the page again just to rerender that also. Still the same issue.

Am I missing something?

Thank you. That option was already ticked.
I’ve also deactivated LiteSpeed Cache and Cloudflare for testing. No change.

Hi,
Thank you for your answer.
I had reported the error also to Brevo. Oddly enough I also noticed that deactivating their plugin removes the error. They just made an update today and fixed the issue.

Dang. That was fast! And works like a charm.
Thank you so much. Will head over to the reviews and give you a five star review. Thanks

You’d add that to the template for your products.

I finally found a solution for this problem by myself, after being sent back and forth between PMPro and MSLMS support.
PMPro said that as I activate the PMPro checkout template and the problem disappears, it has nothing to do with their problem. MSLMS said as above that I somehow modified this template myself. I didn’t and wouldn’t even know how to. I kept searching and searching for where this odd code was from.
In the end I tested out removing various elements from the page in Elementor and found the solution. Removing the checkout shortcode, saving the page and putting it back again somehow “updated” the code on that page. With that this error disappeared.
It’s very strange behaviour, but finally solved the issue.

Hi @stephanstylemixthemes
Thank you for making changes to this part. I just updated the theme to version 4.8.72.
I’m afraid though that the issue persists. Tested in FF, Edge and Chrome.
https://swingdancehome.com/en/membership-account-2/membership-payment/?level=3

• This reply was modified 5 months, 1 week ago by boxhamster.
• This reply was modified 5 months, 1 week ago by boxhamster.

Thank you for your reply. The theme was also updated yesterday (till I get notification from ThemeForest it takes a good few hours actually). I am on theme 4.8.71 as of yesterday afternoon and the problem persists.

Note that PMPro still vies the “3.1 Outdated Template <small>Theme: masterstudy</small>” warning.

I just updated to MS 3.4.4, but the problem continues.
(Note that I have to switch the checkout template on my live website to the PMPro to continue to have functionality). See attached video: https://drive.google.com/file/d/1kR649yeaRKwbJLDesjCbLep3Fhq-g4hj/view?usp=sharing

I’d be grateful for your help. ??

Thank you for providing further guidance and the screenshot.
That is great that exists. I wonder though if it’s the most intuitive for users?

Thank you for looking into the issues.

1: that CSS code fixed the issue. Great!
2a: LiteSpeed Cache is not active for admins and logged in users, so that shouldn’t be the issue. TranslatePress. WPML back then when I looked, didn’t work for me. TranslatePress worked great for me. And you have to understand that it was hard work getting everything translated. Redoing it with WPML is not an option. I’m also a bit frustrated that I always get the same message that TranslatePress is not supported. I know, but not everybody can/wants to use it and I am also not the only TranslatePress+MSLMS user out there.

2b: Excellent. Thanks ??

Hi
The given code only adds some functionality in the backend, so it actually has nothing to do with the theme itself.
I guess I need to figure out now why that code doesn’t work anymore due to a recent update of WC.
Thanks