Nazrinn

I updated it now. All went well! =)

Hi Vytis. I confirm the fix worked and all my images are now loading properly! =)

• This reply was modified 2 years, 3 months ago by Nazrinn.

Oh that’s great to hear!

I’ll check it back when I’ll finish the next iteration of my site then I’ll get back to you on it.

Thanks Vytis!

I did this as well but no luck. The problem persisted.

I won’t test this again in a while but I’ll report if there is anything I find interesting.

Thank you Vytis!

Hi Vitys.

I refreshed cache multiple times on both optimole and LiteSpeed cache. Even after reuploading and renaming my file, my Elementor CSS does not seems to link to the correct URL of the image.

In my media library, the correct URL is https://ml275xldtxd5.i.optimole.com/AuPUZI8.ngNs~26f67/w:auto/h:auto/q:mauto/process:11314/id:89ca02dba99cb5ba3df8bff73e33fee3/https://barbandcarole.ca/pexels-dominika-roseclay-1110562-scaled.jpg. No problem loading that one, but that’s just not the URl Elementor uses…

I tried refreshing Elementor’s custom CSS too, but no avail. I don’t know why it’s always using the wrong URL, and always trying to fetch in https://ml275xldtxd5.i.optimole.com/AuPUZI8.lBBr~27163/, while the working copy is on https://ml275xldtxd5.i.optimole.com/AuPUZI8.ngNs~26f67/. It’s frustrating and only that image too.

I’ve put a temporary image in the meantime, but I know my client would like to keep the old one. Any idea what’s up there?

Great! Thanks you to you and your whole team for your hard work. I’m happy this was resolved. ^^

So would I need to rollback the images if the domain name change still?

I did as indicated and now I’m getting these 3 warnings. These are definitely caused by WPACU, as the warnings go away when I deactivate the plugin.

This seems to happens only on the homepage, too.

• This reply was modified 3 years, 4 months ago by Nazrinn.

Will my settings be erased if I do that?

Is there any plans to make that limit higher?

Interesting. I was unaware this was a bug. I thought it was just an Optimole quirk.

I confirm. I only use the WordPress importer to import images. I never did it otherwise.

When I import posts with the “attachment” option checked during import, medias usually do not import with the post, but I’m thinking this might be the WordPress importer not playing nice with Custom Post Types or media inside an Elementor post, or simply the media isn’t associated to that specific post.

I figured the individual rollback option. However, is it possible to rollback more than 5 images at the time when in the media library in list view? Thanks!

PDF warning.
mp4 warning.

Weirdest thing about it is that WP_DEBUG is commented.

• This reply was modified 3 years, 5 months ago by Nazrinn.

That’s great to hear! Thank you!

Adding an HTML class to lazy-loading images would already help tremendously in “tracking” the image to animate, without adding animation options to the UI.
The latter code block I showed earlier is how I handle animations with LiteSpeed Cache‘s lazy-loading. They made a simple tutorial on how to create a lazy-load animation for their plugin. But of course, I don’t get smart image resize when using LSC for lazy-loading!

For reference, here is an image of LiteSpeed Cache’s lazy load settings. I think Optimole could use something similar to some of those options.

Let me know if there is any more you need.

• This reply was modified 3 years, 5 months ago by Nazrinn.
• This reply was modified 3 years, 5 months ago by Nazrinn.

I have found that I could rollback the missing image via the list view of the media library (for some reason it worked?). However it’s tedious because I could only rollback 5 images at the time, and there was about a few hundred missing.

• This reply was modified 3 years, 5 months ago by Nazrinn.

Okay so yesterday I have discovered one cause for the issue.

For saving bandwidth and server resources, I use Optimole with the CDN on when I make copies of my website for local development and staging, then simply change the URL of the meta box (using Velvet Blues Update URLs plugin
) to correctly point the image URL toward my main domain, where the images are stored in the cloud. It goes a bit like this.

1. Images get uploaded to the live version of the site.
2. I make a copy of my website to my staging and/or local environment using Duplicator Pro.
3. Since all instance of “domain.com” URL gets changed to “staging.domain.com”or “localhost/domain”, I use Velvet Blues Update URLs to update all my image URL to point toward “domain.com” instead (because “optimole.cdn/staging.domain.com/image.jpg” or “optimole.cdn/localhost/domain.com/image.jpg” simply doesn’t exist),
4. Once I am done with developing my feature, I import all new content my clients might have created on the live site to the staging. This requires me to rollback the images on the live site before using the WordPress Importer to transfer my media files. *

So far so good. However, when using the WordPress importer, things can get tricky. I haven’t followed what happened there 100% but I think it’s because I might have duplicated the import. I think something like this happens.

• Image on live site is marked as such: optimole.cdn/domain.com/image.jpg
• Image on staging is normally marked as such: optimole.cdn/staging.domain.com/image.jpg (I do not disable the CDN since image URL should match anyway). The original image should be simply named image.jpg
• However, the image Optimole picks up is called image-1.jpg. This is probably due to the WordPress importer uploading images with the image.jpg name twice in the same day. This create a cdn link looking like this: optimole.cdn/staging.domain.com/image-1.jpg
• Once I push my staging site to live, it changes the staging URL to the live once, converting optimole.cdn/staging.domain.com/image-1.jpg to optimole.cdn/domain.com/image-1.jpg

However, optimole.cdn/domain.com/image-1.jpg doesn’t exist! only optimole.cdn/domain.com/image.jpg does, which results in a 400 error when Optimole try to look at optimole.cdn/domain.com/image-1.jpg in its CDN!

Potential solution: make the local, staging, and live site share the same media pool under the same “domain” in Optimole’s CDN. (Not entirely sure if there is an option for that yet. If so, I haven’t figured it with current documentation.)

* I usually avoid rollbacking my images. The reason being that doing so replace the URL of the image with my local URL (normal) and affect the “last edited” date of my blog posts (undesirable effect) on top of being a lengthy operation. Since the live site will be replaced by what’s in the staging very soon, I don’t care too much about that “last edited” date changes on the live site.

I think there is another case where this 400 error happens where it was truly “random” (no deployment/dev copies installed recently). I’ll let you know when I’ll encounter this again.

Hopefully this helps.

• This reply was modified 3 years, 5 months ago by Nazrinn.
• This reply was modified 3 years, 5 months ago by Nazrinn.
• This reply was modified 3 years, 5 months ago by Nazrinn.