Vitaliy Lyubezhanin

Perfect. That fixed it. Thank you so much.

I can defiantly leave a review without being logged in – you can see here: https://themotionbooks.com/shop/our-wedding-tmb/#reviews (or scroll to the bottom of the review section).

I am not using any third party review plugins, as I understand, WooCommerce is just using the standard comments form and adding a post type to it.

In WooCommerce, I see this setting – so maybe that is why it’s possible to leave a review.

Looking forward to hearing from you and resolving this issue.

The user bought an item from us (most likely as a guest) and then came back to leave a review. They left their name and email in the review section, so we can see who it is. But it would be good to see their name on the review, instead of “Anonymous”

The ones that have an account, those seem to be fine, but the ones that are just leaving a review with name/email, those names are missing from the feed. The review does contain the name on the front end of the website.

That’s the thing.. that the user name is in the review name. So the user name is in the database. As I understand, the user left the name when leaving the review.

I actually have LINK disabled for the LIVE token.

It’s odd that it used to work relatively flawlessly – and now many customers do not get the Apple Pay or Google Pay option.

Yep. That was fixed in latest update.

What I mean is that it has two “” before work lazy, so that might be causing the code to not realize that it needs to lazy load the images.

You can see it here: https://imgur.com/a/jjl4BXN

This is a dev site, so it’s probably connected is safe mode.

We have tested turning off all the plugins, and the only one that would actually make a change to the image url is turning off jetpack (which I can’t for the long term as I need the shipping and tax plugin).

Hey, thanks for responding.

We have testing turning off wp-rocket as well (it was probably one of the first things we turned off to test).

The weird thing is (I’m reiterating), is that I reuploaded the images with a new file name, and somehow it get to WordPress CDN and loading from the i0.wp.com domain.

I have tried replacing the images with new images and at first, it seems to have worked – I was getting images to work from my own server. But all of a sudden, a week later, the same pages have the main image loading form the i0.wp.com image CDN. WHY? I’m not sure. It’s for sure a bug in JETPACK!

The weird thing is, I reloaded the new image (with a new file name), it seemed to have worked. But a week later, I can see that the image is loaded form the i0.wp.com image CDN!!! WHY!!!!

Hey Sandip,

The interesting this is that we never turned on Image Accelerator, but randomly noticed the issue of some images being low quality. So after some investigation, we realized it’s the JETPACK plugin (we deactivated plugins one by one). The only plugin deactivated that would allow the original images from our server to load was JETPACK.

I searched for https://i0.wp.com/themotionbooks.com/ in the database and was not able to find anything.

Replacing the image with a new one (named differently) did the trick. It’s just odd that randomly the jetpack image accelerator caches images.

I’ll also have jetpack purge some of the other images.

Thank you for getting back to me.

The issue I’m running into with just turning on Jetpack (just to calculate taxes), is that some of my images (even though all modules are confirmed to be off) are loading from the io.wp.com CDN – why? I have no idea.

https://themotionbooks.com/shop/personalized-tmb/

The first image loads here: https://i0.wp.com/themotionbooks.com/wp-content/uploads/2020/09/Wedding-Video-Books-CUSTOM-MODERN-LARGE-Front-Gold-300×214.jpg?ssl=1

And it loads in low quality, so that makes it worse. I wish I can override that at least in code somehow as that is popular page and I’d want that image to be clear.

Once you create a connection, can you just disable jetpack?

I want to ask again as I’m seeing this issue still persistent on our website. When disabling JETPACK, the issue is fixed. However, my understanding is that I have to run jetpack in order to use the woo commerce tax plugin – is that correct?