James W.

Can anyone confirm a fix for this issue upon upgrading to 3.26.4?

Thanks in advance!

I can attest to this issue.

Upon upgrading to 3.25.3, an image (specifically in the header) that I had set to be hidden on mobile is now visible. It appeared that vertical spacing between elements in the header was also impacted.

I restored my site as it was before the upgrade, which reverted Elementor back to version 3.24.7, and these issues disappeared.

Now, as @irinelmita mentions above, when in the editor, I can now see that even in version 3.24.7, the “hide on mobile portrait” option is not set for the image in question; it appears that a prior update may have cleared this setting, and version 3.25.3 actually unhides the image on the frontend.

@bobsled, I had the same issue and have rolled back to 4.7.10. @isaumya was this already resolved in 4.7.12?

The issue appears to have been resolved on my end upon updating to 3.6.2. @amandamkelly88 and @thewebatom, does this update address your issues also?

Thank you for your prompt response! Here’s the link sir, https://pastebin.com/jWaXUjNS

it would go against the name of the plugin

Indeed – I get your point there. However, people use your plugin for all sorts of reasons, including the ability to have the images served from your CDN, as well as served as WebP.

My needs are these, specifically because my images are already served in the appropriate size and are being served too small after resizing…and further, if I understood the article correctly, by excluding images from resizing, (even on an individual basis as this article details), this would prevent them from being served as WebP. This would not be a solid workaround, as it breaks the WebP functionality.

Any other suggestions?

@isaumya

Well like I said for the longest time I was using WP Super Cache and it had no issue serving up the WebP versions. It appears there is already an integration with the LiteSpeed Cache plugin in the settings, so I’m curious is there any possible way you can work with LiteSpeed on this incompatibility? I LOVE your plugin and would prefer to continue using it for caching purposes…

Please also note that since I am not on a LiteSpeed server, the caching abilities in LiteSpeed Cache are disabled, so that would not be an option for me.

Thanks again!

Hey @isaumya

I added the following to the .htaccess file:

<FilesMatch "\.(gif|jpe?g|png|webp)$">
<IfModule mod_headers.c>
Header set Cache-Control "no-cache, no-store, must-revalidate, max-age=0"
</IfModule>
</FilesMatch>

but all that did is not cache the png and jpeg files being served; the headers on the images showed “DYNAMIC” which is good…but my issue is they are still being served as png’s and pjeg’s, and not as webp. Am I missing something?

• This reply was modified 3 years, 4 months ago by James W.. Reason: Missing a code line

@isaumya oh I thought those were just for browser caching. Okay I’ll see what I can do.

@isaumya

Excellent, thank you so much for this info! Where would I set the cache-control header value for the images?

@isaumya

Thank you for the response! I understand how and why they are being cached, that’s why I asked how to exclude the image files from the HTML caching this plugin does, so that when CF is rendering the pages to the visitor, it still makes a call to my server for the images and is able to serve up the correct version.

Are you saying that with your plugin, there is no way to fine-tune what is cached and what is not, and that I must look for a different plugin that handles WebP conversions? If that is the case, how would this other plugin be able any different? Would it force the images to be loaded from a different CDN or something of that nature?

Thank you again for your time.

• This reply was modified 3 years, 4 months ago by James W.. Reason: Clarity

@filz51

This issue appears to be cookie-related. Head over to wp-admin/options-general.php?page=wp-cloudflare-super-page-cache-index&swcfpc=1, scroll down to Strip response cookies on pages that should be cached, and select Yes. Click Update Settings, head over to Force purge everything, and let me know!

• This reply was modified 3 years, 4 months ago by James W.. Reason: Add text

@filz51

Would you mind sharing these pages with us so we can run developer tools? Also, check your Cache Behavior Settings under wp-admin/options-general.php?page=wp-cloudflare-super-page-cache-index&swcfpc=1 to see if the pages are check-marked or listed in the URI list.

• This reply was modified 3 years, 4 months ago by James W.. Reason: typo

@gigglesslut420

Thanks for the comment! Yes, currently I only use LiteSpeed Cache for page optimization features (i.e. minification, defer JS, remove emoji, etc.) and image optimization (compression and WebP conversions).

To clarify, I am not using LiteSpeed Cache for caching, never have. I actually can’t if I wanted to because the caching functionality in the LiteSpeed Cache plugin only works on LiteSpeed servers. However, I do rely on LiteSpeed Cache for optimization measures to ensure the pages load fast and that everything is optimized properly before getting cached by Cloudflare.

It just sucks that I lost the ability for the images to load as WebP after switching from WP Super Cache. Hoping the plugin support can provide some guidance on this.

so I now use the WebP Express plugin. Imagify also has WebP in its plugin, and is a little easier to set up (or is less customizable, depending on how you look at it).

Are you saying that with caching done by WP Cloudflare Super Page Cache, WebP Express and Imagify WebP conversions are displaying on the cached pages? I was under the impression that the WebP versions were not displaying due to the fact that Polish is not active on my Cloudflare account, resulting in the PNG’s and JPEG’s being displayed instead.

UPDATE: ManageWP has released an updated version (4.9.10), which appears to have fixed the issue from their end. I guess they heard enough of our complaints and took the liberty to patch as promptly as possible, more or less what I was hoping y’all would do instead of waiting for 3.0.0.

Anyways, hope this helps!

*Resolved*