Kamil Chmielewski

It’s problem with comment appended to site’s html – Weston Ruter found it out, apparently he already posted you an issue on github.
https://www.ads-software.com/support/topic/amp-not-working-with-litespeed/#post-12716486
https://github.com/litespeedtech/lscache_wp/issues/212

Thing is, I don’t have this error too now, dunno what’s changed. Thing is, there is still an error ‘URL validation failed due to unexpected JSON in AMP validation response’ when I try to validate any post, so I’m not sure if it’s actually working.

Funny thing, it’s not present now – dunno what’s changed, as I have auto-updates turned on. Maybe one of mentioned plugins changed, maybe it was another plugin that was interfering with LiteSpeed.
So, is_amp_endpoint() is no longer an issue, but json fetch is still failing with LiteSpeed turned on, and works fine with disabled. Tried to turn off option by option in LiteSpeed configuration, including lazy load, purging cache after every change, but it’s still the issue.

I’ve activated Twenty Twenty theme, activated LiteSpeed plugin and AMP plugin (https://www.ads-software.com/plugins/amp/), set AMP mode to ‘Standard’ in settings. It shows error that it couldn’t retrieve amp status due to failed json fetch. Then I just open any page or post, and the ‘is_amp_endpoint() was called before …’ errors pops up

https://www.ads-software.com/plugins/amp/

• This reply was modified 4 years, 7 months ago by Kamil Chmielewski.

I was able to replicate issue on local environment. I’ve installed AMP and lightspeed cache on fresh wp, activated twenty twenty, both plugins and amp is broken. Deactivating lightspeed makes it work.

I was able to replicate issue on local environment. I’ve installed AMP and lightspeed cache on fresh wp, activated twenty twenty, both plugins and amp is broken. Deactivating lightspeed makes it work.

Mo?e nie tyle nietypowe, co rzadko u?ywane – wi?kszo?? autorów daje ustawienia w ustawieniach. Ale po?o?enie w wygl?dzie jest jak najbardziej zasadne. Warto, by inni autorzy pluginów zmieniaj?cych wygl?d strony dawali tam konfiguracje swoich wtyczek.

Before the thread will be closed, I’ve scanned PressWork with AntiVirus plugin, and it found
function pw_add_custom_css_file()
which, in it’s opinion, can be dangerous. I don’t know how, but maybe it loaded something external. Anyway, I’ve deleted this function, and it has no impact on how site works. Time will show, if that will get rid of those errors. If it won’t help, I will consider changing theme then.

Well, if you say so. I like this theme. Do you know any similar? Or, at least, such professionally looking free theme? Anyway, the thread is to be closed.

So you claim, it’s theme’s fault? I can’t see why? But ok, since presswork.me is not leading anywhere now, I’ve cut it from every single place. Or is there any code, that’s causing all this mess? But I’ve never dealt such errors, and I’ve been using this theme since beginnig of this year.

Read my edit please. I possibly can delete every occurence of presswork.me, but how could it help?

Developers of PressWork have given up, abandoning this theme. Look at https://twitter.com/PressWorkWP

edit:
Are you suggesting, that deleting presswork.me adress from everywhere in theme files could help? I don’t see a way, that this theme could cause this problem, because I’ve been using it for very long time, even back when my domain was kamster.tk. And there were no such problems.

Yes, ofc, using many plugins, but none of them worked in this case (well, they are working, sice ‘normal’ overhead is deleted, but 4 mb in each of mentioned tables still remains)

Now I’ve noticed, that number of tables with incurable overhead is bigger. Now it’s about 20 mb (5 tables, each with exactly 4 mb of overhead), while my whole db is about 8 mb. These tables are:
options
postmeta
relevanssi
statpress
wfFileMods
Is there any connection between that, and 404s?