Why Optimus with Cache Enabler

There is no “Cache Enabler” checkbox in WebP Express… ?

Hah, sorry let me explain better. The WebP Express text says:

In combination with Cache Enabler, the same as above can be achieved, but with page caching.

So I installed Cache Enabler (instead of my usual WP Supercache)
Cache Enabler has this checkbox where you can generate two seperate cached pages, one with webp and one without.

When this box is checked, the whole page breaks. I’m assuming because the preferred Optimus generator was not used, but your WebP Express.

I guess my question really is, what would be the best settings for WebP Express to allow for serving cached pages?

I’m curious to why it breaks and under which circumstances. Of course it shouldn’t!

As it broke when you installed Cache Enabler, I suspect that Cache Enabler is to blame. Could you try to disable WebP Express? I bet that it still breaks.

Cache Enabler should not be breaking anything without Optimus. Cache Enabler isn’t dependent upon Optimus, and doesn’t call it directly. Instead it simply alters the HTML so urls pointing to jpegs and pngs are pointing to webp’s – WHEN IT DETECTS THAT A WEBP EXISTS (in same directory, same name, but with “webp” extension instead of jpg/png) – and only when the browser that is visiting supports webp.

WebP Express steps in *instead of* Optimus – but you must configure WebP Express to put the webps in same dir as originals, and with right extension.

With both WebP Express and Cache Enabler installed, both will be doing HTML altering (if you activated it in WebP Express). Unfortunately you cannot disable it in Cache Enabler. That would have been nice. Usually it should do no harm to have it running twice. But if it is the HTML altering in Cache Enabler that crashes, it *really* would have been nice to be able to disable it.

What we want Cache Enabler for is to maintain two separate page caches – one for webp-enabled browsers and one for “webp-disabled” browsers.

The major benefit of using “Replace Image URLS” rather than picture tags is that it also replaces background images in inline CSS. If you do not have any of these, switch to picture tags syntax (and you won’t be needing Cache Enabler).

Activating WebpE with Replace image URLs option
No caching plugin activated. Frontend all OK.

Activating Cache Enabler.
Saving settings (No minification, pre-compression or dual cache)
Frontend all ok at first page open

Reloading the page (Ctrl + f5) my site now displays a full page of this:

?}?v?F??o?y?<??1@??DI???dˉ???v????iM

So I’ve been testing this and it seems that Webp Express has nothing to do with it. When I disable the plugin I get this rubbish text whenever I refresh a page.

I guess I’ll uninstall Cache Enabler, get support there and go with the picture tag for now ??
Thanks!