everade

@daanvandenbergh
Any news on this? I have no idea what clears the error log, i really searched the entire source of my website including plugins. But the main culprit isn’t really about the cleared logs but the issue that the website tries to load fonts from non existing folders.

Probably a bug in OMFG when setting up custom “don’t load” settings in the free version?

@daanvandenbergh

I found a single console.clear() within my theme code, however it’s only in a single function that seems to related to the admin section when uploading a video file.
I’ve commented it regardless and cleared the cache.
Don’t see the errors still when loading the website, so i assume there might be still something else clearing the console. But i ran a search through the entire website code and wasn’t able to find another clear anywhere else.

• This reply was modified 11 months, 1 week ago by everade.

@daanvandenbergh

Ugh?! I’m not aware of any such code. Do you have a snippet of it so i could search for it? Could it possibly be Cloudflare related?

Thanks Daan !

Just seems weird to me that instead of MailPoet devs actually going ahead and removing or fixing that error condition, now me the user is supposed to do a workaround just so my logs don’t fill up with an unnecessary error message which supposedly isn’t even an error.

I’m already running a linux cron, yet the errors are still being generated. Keep in mind that this is a MailPoet error, generated by MailPoet, logged into the MailPoet logs.
Please also note that these errors are generated when navigating throughout the MailPoet plugin. Validate your Activation Key? Error logged (despite displaying YOUR KEY IS VALID). Do nothing? Error logged. So basically all the time. Just every time MailPoet checks the activation key for whatever reason, it logs an error, despite having a valid Key entered. This doesn’t seem to be related to the Cron at all.
It’s just MailPoet which runs a key-validation all the time when using MailPoet, then triggering an error for no apparent reason. So i’m not sure how editing the wp-config file is supposed to remove an error condition that’s been coded into the plugin source code. Doesn’t make any sense to me at least.

The home-url in that error looks correct to me by the way (it’s simply my base URL such as https://redacted.sdf ) So i’m not sure why the key-validation is failing when in my Key Activation settings the Key is valid. I don’t have premium, never used premium, i use the free version, so the key entered is a free key, and i use free features only.

Any explanation or hopefully a fix?

• This reply was modified 11 months, 1 week ago by everade.
• This reply was modified 11 months, 1 week ago by everade.
• This reply was modified 11 months, 1 week ago by everade.
• This reply was modified 11 months, 1 week ago by everade.
• This reply was modified 11 months, 1 week ago by everade.

No i’ve cleared both CDN and LightSpeed Cache multiple times by now and PageSpeed still reporting the same errors in the “Best Practices” section on both mobile and desktop tests. You must have missed it because it’s also in your own example you just shared. Just scroll down to the “Browser errors were logged to the console”.
https://i.postimg.cc/3rC1xPyT/image.png

@qtwrk
Is there any specific reason why LiteSpeed Cache sets the mod_expires by default to A31557600 instead of A31536000 ?
1 year equals 60s * 60m * 24h * 365d = 31536000

Also these are deprecated:
ExpiresByType application/javascript A31557600
ExpiresByType application/x-javascript A31557600

And if i recall that correctly then jpeg already includes jpg, so the mime-type jpg is redundant.

Not sure about x-font-tff and x-font-woff, but i assume those could be deprecated as well.

Just letting you know. Maybe you have reasons to add these.

Yes it was indeed the culprit.
Thank you so much!

@battouly
Request 7398172

Generated via the pre-sales contact page, so not on this forums.
I’ve already recieved some answers there, but haven’t heard back since the last time (6. december) I’ve answered further questions about which mails I’ve been testing with.

That is already the case. On CF the Browser Cache TTL is set to “Respect Existing Headers”

So i guess this one here is the culprit then
It’s set in the mod_headers.c :
Header always set Cache-Control: max-age=31536000

I assume that overwrites the mod_expires.c definitions created by LightSpeed Cache?!

By the way, thank you very much for your support despite already having pointed out that it’s not casued by LightSpeed Cache, really appreciate it!

I’ve no idea what i’m supposed to look for.
Basically everything is loaded from local cache, including the main .php file from each page.

General
Request URL:
https://redacted.website/wp-admin/plugins.php
Request Method:
GET
Status Code:
200 OK (from disk cache)
Remote Address:
[redacted:redacted:redacted:redacted:redacted:redacted]:443
Referrer Policy:
no-referrer-when-downgrade

 Response Headers
Alt-Svc:
h3=":443"; ma=86400
Cache-Control:
max-age=31536000
Cf-Cache-Status:
DYNAMIC
Cf-Ray:
redacted-MXP
Content-Encoding:
br
Content-Security-Policy:
upgrade-insecure-requests
Content-Type:
text/html; charset=UTF-8
Date:
Thu, 07 Dec 2023 16:43:24 GMT
Expires:
Wed, 11 Jan 1984 05:00:00 GMT
Permissions-Policy:
camera=(), microphone=(), geolocation=(self), fullscreen=(self)
Platform:
hostinger
Referrer-Policy:
no-referrer-when-downgrade
Server:
cloudflare
Vary:
Accept-Encoding
X-Content-Type-Options:
nosniff
X-Frame-Options:
SAMEORIGIN
X-Litespeed-Cache-Control:
no-cache
X-Turbo-Charged-By:
LiteSpeed
X-Xss-Protection:
0

First and foremost. No…
I’m not re-posting a screenshot i’ve already posted.
And secondly, no i’m also not going to tell the MailPoet support where the MailPoet Logs are. I said the errors are generated when visiting the MailPoet Home section. Not that the MailPoet Logs are to be found there.

And third, no, i’m for sure not showing you the link to the other support case if you’re not even capable of this.

What a waste of time.

There you go, again…

Still getting hundreds of errors per week filling up my logs for no apparent reason.

Hey Elvira.

The definition of an error is that something went wrong.
I don’t understand why it would generate an error just because i’m using the free version.

This shouldn’t generate an error. It just bloats my error logs with a behavior you claim to be normal. If it’s normal, then it should not generate an error.

But yes, i have issues that consecutive mails aren’t sent, but i’ve opened another support topic for that but i’ve not recieved proper support in 6 months.