soupia18

Came here also for the webp support. Is this working?

Hi there – thanks for the response and the info to remove the noindex.
Greatly appreciated.

I can’t say at the moment because I had to disable the GM – it’s an important site at a critical season – having the most important pages hidden from SERPs is totally killing the business.

I will have to find a way and the time test this somehow —

Report Number: ETANODNP

It looks like there is something that Google Bot don’t like, or possibly can’t access.

It’s the second time that I enabled the Guest Mode on this website and Google started completely hiding the page from search results (like it’s not in the index). The page was off of the SERPs for 10 minutes, then back to the SERPs for 5 minutes – Until I disabled Guest Mode and the page settled back to the SERPs without problems.

Checking with the webcache.googleusercontent.com – The page was plain html, without styles and probably js.

Using the various tools from Google (live test, rich snippet, mobile test), one time the crawler reports fine, the next time it reports that the page has problems (e.g. it’s not mobile ready).

That’s sad

Report number: ETANODNP

In CloudFlare, I had enabled the Cache Everything (html cache) – which I disabled recently to test.
At the same time, I used the APO service – because from my research it was the only way for CloudFlare to cache separate versions of the webpages per device, otherwise I was getting desktop layout elements on mobile devices and the opposite.

So – after having post here and in Cloudflare – and after re-considering the whole issue – I guess what I am looking for is a proper way to cache my pages in CloudFlare’s network servers and keep it synced when there is a change in the origin – e.g. like when a combined JS file from WP LSCache plugin has regenerated.

How, could I signal this to CloudFlare to re-cache a specific page when this happens?

On another note, I see that a js file can be regenerated without doing anything particular on that page (not after saving it anything else).

An example of an expired JS file that ends ups to a 404 error.
Now this occurs on Firefox and Opera, but Chrome is loading correctly.

wp-content/litespeed/js/61f7dc494f2fdc5dd17dd7f4e97e8265.js?ver=4627f

And these are the headers of the file:
cache-control private, no-cache, no-store, must-revalidate, max-age=0,no-transform

cf-cache-status BYPASS
cf-ray 6e19a373a9726f32-ATH
content-length 1238
content-type text/html
date Tue, 22 Feb 2022 16:37:21 GMT
expect-ct max-age=604800

nel {“success_fraction”:0,”report_to”:”cf-nel”,”max_age”:604800}
pragma no-cache
referrer-policy no-referrer-when-downgrade
report-to {“endpoints”:[{“url”:”https:\/\/a.nel.cloudflare.com\/report\/v3?s=4tilqvfvTZ13k638iKtPtSqw2IPSOtZRBbqlJxdpIgKlFbwCK2r%2FKH7M4i%2FZ9tdJCav29kE25sBrwMXMQuSxk94epkjJjpBI4%2FMBx19JJnzkNcpCNLAES4%2FMMtzt9ZrjQX82w62XczCvqvfwgcm8wK%2Bqzg%3D%3D”}],”group”:”cf-nel”,”max_age”:604800}

server cloudflare
strict-transport-security max-age=31536000
vary User-Agent, Accept-Encoding
x-content-type-options nosniff
X-Firefox-Spdy h2
x-turbo-charged-by LiteSpeed
x-xss-protection 1; mode=block

At the same time in Chrome, I am loading the correct combined js file
/wp-content/litespeed/js/78945092b38ddd396dd11264f2ad6e93.js?ver=4627f

I have to add that the issue many not occur with all the browsers at the same time and maybe with all the users. So, I might experience the issue with Chrome but not with Firefox and/or a customer might be getting the issue, while I am not.

Hi @wfpeter!
Thanks once again for getting back.

The problem is that I don’t see binary values in the database of the live website. Shouldn’t those IPs be stored as HEX values or something?

Instead an IP looks like ??.é
Can this transformed back to a HEX represantation?

*What do you think if I would deactivate and delete WF, delete its tables and re-install?
Could that solve the issue with the values not being saved as binary?

Hi @wfpeter – thanks for the prompt and helpful response.

One note is that all existing data in the database of the production site looks like this and not only the dumped data.

So for example currently all IPs in any WF db table are stored like this ” ??.é “.

Is this normal to see the data stored in the database like this?

And does this make any difference to what you have suggested above?
Will the –hex-blob argument will help with the dumped data?

The issue occurs when in the notification email someone selects to include date smart tags.
It then has to run the code at the line 272 where it calls wpforms()->entry, but the entry property there it’s null – so that’s why it fails with a fatal error.

Same error here.
Form can not be submitted.

i also just tried this:

I made my jQuery id selector more specific, by adding the #widgets-right #myelement, so it selects the widgets from the sidebar’s side.

This way it works.

ok – that’s so strange :
if I attach jQuery based on class instead of elements’ id the code works…