atutrabajo

Hello Marko. First of all, thanks for responding so quickly (As always, bah:).
Having said that. Several things regarding your answer:

• As for…
  …”depending on what is changing, for example the style, it means that the CSS has changed”…
  I tell you that, NO, Never, Never Change the CSS or ANYTHING in the header and/or footer for several MONTHS (When I finished defining it).
• Regarding…
  …”so you should also update the media query strings in the browser Cache”…
  It’s what I ALWAYS do. However, when I do it in ANOTHER browser than Google Chrome, these errors (in the header/footer), remain.
  That is to say, as I said, I have to edit the page in a browser and then go to Google Chrome so that these errors are “cleaned”.
  It’s more…
  When I work EVERYTHING in Google Chrome, I don’t even need to clean up the query strings every so often (as you say). I simply finish editing whatever page it is, save the changes, clear the cache in Cloudflare and soooo! The changes are reflected PERFECTLY and neither the header nor the footer are modified or give the error that I showed you in the screenshots.
  In fact (another detail)…
  The ONLY page the error appears on is ALWAYS the one I’m editing on. ALL the others, remain as is (as it should be) because, the header/footer is the same in ALL () () Except in those sales pages in which, for “marketing reasons” (put it), I remove the header and/or some part of the footer so that readers are not “distracted”, heh.
• Regarding…
  …”Once you update the query string and purge the cache, any browser should get the new, updated file”…
  This is so. AND NOT. I explain…
  What does update is the text. That is, what I added/corrected/whatever. But…
  The header and footer are AUTOMATICALLY “disconfigured” (As I showed you).
• Linked to…
  …” Does this only happen while logged in or once the page is edited, does the problem occur in incognito mode (logout)?”…
  I do not understand the question. But, just in case, I will explain my “procedure”;
  a) I open any browser other than Google Chrome (And I tried +10, heh)
  b) I copy and paste the url of my WordPress admin panel
  c) I go to Pages/Edit page and open the one I’m working on
  d) I edit a part (I add text/images/whatever)
  e) I save the changes
  f) I go to Cloudflare and clear the cache of THAT page
  e) I go to an incognito window and boom!

And the “curious” thing is that when I do all this in Google Chrome this problem does NOT appear.
It’s more…
When I work everything in another browser and then go to Google Chrome/Incognito window the problem “remains”.
So, I have to do it all over again but, with Google Chrome. That is to say;

• I reopen my administration panel
• Cleaned ALL caches (Including Media)
• I clear (again) the Cloudflare cache (but open in Google Chrome) and soooo! () () In fact, before sending you the correct “samples”, I had to repeat this SEVERAL times, heh.

Finally and linked to…
…” What are the changes you are making to the header/footer?”…
Like I said, it’s been MONTHS since I made ANY changes to these elements on my site.

I hope it is understood.

I await your comments.

From already thank you very much.

Hello. Just to close this ticket and, so that those who may have the same problem described here, know how to solve it.

It turns out that, when I did some modification (for example, upload a script in this plugin), I got the mentioned problem.

But then (for example the next day), the problem “disappeared”.

And what was happening? Simple.

On my site, I have the W3TC caching plugin installed.

For those who don’t know, the cache is loaded when a visitor enters. Peeero… W3TC, has a configuration that causes, every X time, the pages are “preloaded”.

In this way, even if one does not have visits, when a new visitor enters, the page will already be “preloaded”.

That’s why, the problem described in this ticker “resolved” itself, heh.

And why wasn’t it resolved immediately if I cleared ALL the caches? Well.

The following happened…

It turns out that, in my eagerness (almost obsession, heh) to optimize my site, I had read somewhere that, I could go to Cloudflare / Rule of pages / Cache ALL the browser.

And on top of that, I had it in 6 months!, heh.

Ergo. On the one hand, it was cleaning all the caches and on the other hand, it was telling Cloudflare to, keep ALL the browser for more, time, heh.

Conclusion: I removed that rule, cleaned all the caches and soooo! As we say here “holy remedy”.

Therefore, I close this topic and I hope that this information can be useful to someone.

See you.

Dear friends: I am writing to inform you that, related to this ticket/problem, I think…I found the “solution”!, heh

First of all, you should know that what I “discovered” is that the “problem” was generated by myself, heh.

Because? Well. I’m going to explain…

It turns out that, in my eagerness (I would say obsession:) to “comply” with Pagespeed, I read ALL the material, there was and by proxy (Yes. The classic problem of “infodemic”, heh).

And among so many things, I found a tutorial that showed how to improve the initial response times of the server.

And for that, among many other things, he told us to go to:

And among so many things, I found a tutorial that showed how to improve the initial response times of the server.

And for that, among many other things, he told us to go to:

Cloudflare/Rules/Page Rules/Browser Cache TTL…

And on top of that, at the beginning I had given it 1 year! (*)

(*) Although later I lowered it to 6 months, heh.

So what was happening? Simple.

On the one hand, I was telling Cloudflare in Caching/Configuration to…”Respect existing headers”… and, on the other, I was telling it to keep them for 6 months, heh.

Anyway.

Ergo. What happened is, I cleaned and cleaned but, until Cloudflare “craved”, the changes in the browser were NOT reflected.

Conclusion: I removed that rule and soooo! The “problem” was fixed.

But EYE! Even so, today (which was when I realized it and that’s why I’m here, heh:) I made a small change on a page (To be more exact, I removed 2 words and added 2 emojis) and AGAIN I had the same problem.

And then? Simple.

As it turns out, until the preload does NOT (AGAIN) preload the ENTIRE page in question, the change will NOT be seen immediately.

Therefore, what needs to be done, is to Clean EVERYTHING (Minified+Media+Page) with EVERY change.

Whether this is a “nonsense” or is “giant”.

Conclusion:

Now that I know all this, whether I have to make a small or big change, I write it down and try to “put them all together”.

This way, I do the ENTIRE cleanup process (Minified/Media/Page) in one pass.

Definitely…

I just wanted to record this “discovery” in case the same thing happened/happens/will happen to someone.

I hope it’s helpful, and of course I’m assuming THIS issue is ALREADY resolved (and I’ll flag this ticket as such).

See you.

Hello. I didn’t answer you before because I was “testing” SINCE the moment I updated your plugin.

Ergo. I am hereby informing you that… I think the problem has been FIXED!

I explain:
I updated the plugin the day before yesterday and since then performed the same tasks that – “I suspect” – was causing the error described when starting this ticket.

And, for 2 (two) days, NONE of the errors appeared again in my “error log” file.

So, CONGRATULATIONS.

Therefore, I am going to mark this ticket as solved.

For now it’s all.

Again, thank you so much.

Greetings.

And how’s it going? This is just to “remind” you that as of today I am still getting the SAME errors.

This is…

…”[Wed Mar 15 12:52:36.101631 2023] [:error] [pid XXX:tid XXX] [remote XXX] PHP Warning: Attempt to read property “post_type” on null in /home/XXX/XXX/wp-content/plugins/joli-table-of-contents/core/Controllers/PublicAppController.php on line 165“…

…”[Wed Mar 15 12:52:36.100028 2023] [:error] [pid XXX:tid XXX] [remote XXX] PHP Warning: Attempt to read property “post_content” on null in /home/XXX/XXX/wp-content/plugins/joli-table-of-contents/core/Controllers/PublicAppController.php on line 22“…

I hope they are resolved as soon as possible.

See you.

• This reply was modified 1 year, 8 months ago by atutrabajo.

Hello Marko. Thanks for answering.

And yes, the site in question is stage9.atutrabajo.org and, as I said, the problem is “occasional”.

This is, sometimes it happens (like the screenshots I sent you), and sometimes it doesn’t.

In fact, in an incognito browser, it works fine for me. But, when I send a link out there (for example by mail), the site that, obviously, will be seen in a “normal” browser, looks HORRIBLE.

And I understand that it is a cache issue + minified because, after a while of making a change (editing) a page or an entry, the problem is solved.

Because? Because in my W3TC I have activated the page preload in 10 pages every 10800 seconds (3 hours). And, since I have 32 pages + 8 posts (40 pages), the ENTIRE site is preloaded, every 12 hours.
But NOBODY is going to come back 12 hours later yes, the 1st. Once you enter, the site looks “ugly” and/or the numerator is set to 0.

I hope it is understood.

Greetings.

Another yes, I say.


Oh. I forgot that – also – I have the following problem…


https://ibb.co/6N58Sbc


As you can see in the screenshot above, in addition to a header and a footer, created with the Elementor Header & Footer Builder plugin, precisely in an Elementor template (Hello Elementor) which, in case you don’t know, comes without these elements (neither header nor footer), in my hompage (the one you see in the screenshot), I chose to add a numerator.
The same (included in the plugin), loads (or should load), from 0 to certain numbers (*)
[(*) I have to update them but, for now they are; 249,682, 415,910 and 14,000,000]


The problem is that, from time to time, what you are seeing in the screenshot happens.
That is to say, the numerator does NOT work! (**)

[(**) And that, what you are seeing, is in an incognito window]


And this, just as I told you about the header, is also “fixed” if the visitor refreshes the page. But you and I know that this will NOT happen if said visitor does not think it is necessary.


Ergo. The numerators will remain at 0 and will generate the opposite effect to the one I am looking for (***)

[(***) This is to let them know that they actually have A LOT of employment opportunities, heh]


Finally, and regarding this last inconvenience:
If you want, you can analyze my source code to see if there is something from all the files (JS and/or CSS) that, I am;
a) Minifying + Adding to the Head + Not blocking using async and/or
b) Minifying + Adding before closing the body + Not blocking using defer and/or
c) CSS minify settings: Enable
Minify method: Minify only
Minify engine settings: Remove protected comments (does not apply when “merge only” is active)
Line break removal (does not apply when “merge only” is active)
@import handling: None
d) Loading scripts after a timeout when there is no user interaction (5s) but NO Minification (****)

[(****) The latter, of course, I do with another plugin – Flying Script – well, yours does NOT have it]

Note:

Just in case, the scripts that are in a) are NOT in b) or d) and vice versa ??

I await your comments.

Like always, thank you.

Greetings.

Hello. It seems that you were right (put it, heh:).

After, following your instructions, I deactivated the mentioned option from your plugin, I already did several tests and in ALL of them it gave me that…
…”No recent web server errors exist for your domain: mysite.org“…

Ergo, in that sense, apparently the problem would be solved, heh!
However, like the plugin functionality, it is one of the ones that I highlight the most and, I need to, I am going to describe what I did.
a) I disabled the mentioned functionality (Preload Featured Images)

b) I “replaced” it with the following code in my function.php…

/* 27) Preload (preload) the featured image in each post */
add_action(‘wp_head’, ‘preload_post_attachment_image’);

function preload_post_attachment_image(){
if (has_post_thumbnail()) {
$attachment_image = wp_get_attachment_url( get_post_thumbnail_id() );
echo ”;
}
}

(*) In case anyone is interested: I extracted this code from;
https://precisefuture.com/uncategorized/preloading-heavy-images-in-wordpress/

c) I checked EVERYTHING again and… soooo! There were no more errors

I hope that this can be of some use (to you and/or anyone reading this thread).

See you.

Hello. Well, frankly, I DON’T know what else to do anymore because I’m seeing (again) the SAME errors that I started this ticket with. That is…

[Thu Feb 02 13:02:34.111139 2023] [:error] [pid 2256614:tid 47495717758720] [client 52.167.144.45:0] PHP Warning: Attempt to read property “ID” on null in /home/myuser/mysite/ wp-content/plugins/optimize-more-images/includes/classes/partials/preload-featured-imgs.php on line 150

And, to top it off, now – also – he messes with my login???…

[Thu Feb 02 15:32:14.305887 2023] [:error] [pid 4166302:tid 47495673632512] [remote 202.131.227.181:0] PHP Warning: Attempt to read property “ID” on null in /home/myuser/mysite/ wp-content/plugins/optimize-more-images/includes/classes/partials/preload-featured-imgs.php on line 150, referer: mysite/wp-login.php

Please, if they are (or are not) you and/or it is Pagespeed’s “fault”, let me know so that I can stop screwing with this.

I await your comments.

Regards.

PS: One way or another, remember that I still need to install/test a couple of optimizations from the list I sent you.

Something that, if I don’t fall asleep before, I’ll start, right now, heh.

Hello Marko. No problem. Anyway, I still have my visitor and like it or not, he needs my attention, heh.
Ergo, until now, I could NOT continue testing (checking) with the optimizations below the indicated line. That is, from the one marked as 15) onwards. Well, if you have any news, let me know.
For my part, only tomorrow (I think, heh:) will I be able to resume my tests.
See ya.

Hello. You’re right. I don’t know what you (or they) did but, since the update to Elementor 3.10.1 the Message did NOT appear again.

And, in case there were “doubts”, I just updated to Elementor 3.10.2 and the message in question did NOT appear either.

Ergo, I imagine that the problem has ALREADY BEEN SOLVED!!!

Anyway, thanks for answering.

For now it’s all.

Regards.

Another yes, I say…

When I wanted to enter Yoast/Adjustment to take a screenshot and send it to my hosting (because of another error I’m dealing with them), it AUTOMATICALLY gave me “Error 520” (Cloudflare) in my browser and, in my cPanel/Error, The following appeared to me;

[Fri Jan 27 23:38:08.781207 2023] [:error] [pid 1133897:tid 47495671531264] [remote 79.124.49.10:0] PHP Warning: Attempt to read property “ID” on null in /home/myuser/mysite/ wp-content/plugins/optimize-more-images/includes/classes/partials/preload-featured-imgs.php on line 150, referer: https://mysite/.env

Do you have anything to do with it?

Why…

I don’t know if it was a coincidence or that ID belongs to you and – perhaps – they were testing something.

What do I know

Anyway.

I await your comments.

Regards.

Hello. Me again, heh. I have a good and a bad one for you:
The good news, I already “discovered” (I think) where the problem is.
The bad, I have no idea if this is good or bad, heh.
I will explain:
In my “zeal” (someone would say obsession, heh:), to optimize my site, I had read (among the thousands of things I read because I understand NOTHING about this, heh), that it could be added to my function.php some codes like these;
https://docs.google.com/document/d/1JSN-qFmgzAwV2B5AYdmQHUd7gNXfGng5/edit?usp=share_link&ouid=102851233358919075037&rtpof=true&sd=true
As you can see, there are (were) about 26(twenty-six) optimizations. And I say there was because, if you look (OK) there are codes that are NO longer there and, in the same line is why () () If you notice ALL the codes, they are headed (commented) with an explanatory line that starts with the // plus an order number.

For some strange reason that I do not know, suddenly, the site began to have a series of “strange” behaviors and, when I consulted with my hosting, they “threw” me (among others), the error that your plugin generated (And it gave rise to to this ticket).
Of course, I sent ALL the developers of the “compromised” plugins lines like the ones I sent them, and while I waited for their responses, I continued to investigate what was going on.
One of the things I tried, obviously, was to replace the theme that’s in use and soooo! The error “disappeared”.
Ergo. As said theme (Hello Elementor Child) has been installed for a while and, it was the 1st. Every time I had this problem, the “logic” indicated that the problem was NOT the theme, but what it contained.
And as precisely, the detailed functions are installed in the function.php of said child theme, I tried, reactivating the child theme but removing said functions and soooo! The error disappeared.

Conclusion (Not to make it longer, heh).
One (or several) of those functions, were generating the error(s) that my hosting attributed to those error codes that I sent to the plugin developers (like you, heh).
Ergo. Since I didn’t know which one of those function(s) it was, I started to;
a) Install each feature (One at a time)
b) Test the ENTIRE site
c) Verify if the error(s) reappeared.

Now to finish. Until now the errors that (supposedly) your plugin generated did NOT appear again. But…
Until yesterday, I had tried with (almost) half of the functions, so I had to sleep, heh.
In fact, if you look (well) at the list, you will see that almost halfway there is a line that says…

Until here (Day I)

Well. That’s because, precisely, I got there with the tests, heh.

In short, if I were you, I would do the following;
1) I would see if, in the list of optimizations that I attached, there are some/s that can generate a behavior of your plugin like the one described in the error that appears.
2) If so, I would reconsider the instructions they sent me to “fix” the problem.
O well. If you think that all this that I described has nothing to do…
3) I would reiterate what they want me to do.

I await your comments.

Regards.

PS I: As I said. The problem with your plugin is NOT anymore. But…
As I still need to install, test and verify the optimizations below the line in question, tomorrow I will tell you how it went, do you think?
For now, that’s all from me.
You (who surely know more about programming than I do) for your part, if you wish, can analyze the optimizations in question. And, if you see something that helps me not to continue analyzing one by one, let me know, okay?
P.d II: And if after analyzing all this, you still think that the routine you mentioned should be followed, let me know. Dale?
P.d III: It was (too) late for me here. Ergo, I’m going to sleep because tomorrow my son comes to visit me. And, precisely for this reason, tomorrow (nor) will I be able to do the tests that I need () () Unless I do them when my son falls asleep or when he leaves, heh.
Therefore, if you wish, you have at least (almost) all day tomorrow to tell me if any of the optimizations that I need to (re)test (since 15), have (or could have) something to do with the problem that gave rise to this thread.
See ya.

Hello. Me again, heh. I have a good and a bad one for you:
The good news, I already “discovered” (I think) where the problem is.
The bad, I have no fucking idea if this is good or bad, heh.
I explain:
In my “zeal” (someone would say obsession, heh:), to optimize my site, I had read (among the thousands of things I read because I understand NOTHING about this, heh), that it could be added to my function.php some codes like these;
https://docs.google.com/document/d/1JSN-qFmgzAwV2B5AYdmQHUd7gNXfGng5/edit?usp=share_link&ouid=102851233358919075037&rtpof=true&sd=true
As you can see, there are (were) about 26(twenty-six) optimizations. And I say there was because, if you look (OK) there are codes that are NO longer there and, in the same line is why () () If you notice ALL the codes, they are headed (commented) with an explanatory line that starts with the // plus an order number.

For some strange reason that I don’t know, suddenly, the site began to have a series of “strange” behaviors and, when I consulted with my hosting, they “thrown” me (among others), the error that your plugin generated (And it gave rise to to this ticket).
Of course, I sent ALL the developers of the “compromised” plugins lines like the ones I sent you, and while I waited for your responses, I continued to investigate what was going on.
One of the things I tried, obviously, was to replace the theme that’s in use and soooo! The error “disappeared”.
Ergo. As said theme (Hello Elementor Child) has been installed for a while and, it was the 1st. Every time I had this problem, the “logic” indicated that the problem was NOT the theme, but what it contained.
And as precisely, the detailed functions are installed in the function.php of said child theme, I tried, reactivating the child theme but removing said functions and soooo! The error disappeared.

Conclusion (Not to make it longer, heh).
One (or several) of those functions, were generating the error(s) that my hosting attributed to those error codes that I sent to the plugin developers (like you, heh).
Ergo. Since I didn’t know which one of those function(s) it was, I started to;
a) Install each feature (One at a time)
b) Test the ENTIRE site
c) Verify if the error(s) reappeared.

Now to finish. Until now the errors that (supposedly) your plugin generated did NOT appear again. But…
Until yesterday, I had tried with (almost) half of the functions, so I had to sleep, heh.
In fact, if you look (well) at the list, you will see that almost halfway there is a line that says…

Until here (Day I)

Well. That’s because, precisely, I got there with the tests, heh.

In short, if I were you, I would do the following;
1) I would see if, in the list of optimizations that I attached, there are some/s that can generate a behavior of your plugin like the one described in the error that appears.
2) If so, I would reconsider the instructions you sent me for your code
O well. If you think that all this that I described has nothing to do…
3) You reiterate to me what you want me to do.

I await your comments.

Regards.

PS I: As I said. The problem with your plugin is NO LONGER. But…
As I still need to install, test and verify the optimizations below the line in question, tomorrow I will tell you how it went, do you think?
For now, that’s all from me.
You (who surely know more about programming than I do) for your part, if you wish, can analyze the optimizations in question. And, if you see something that helps me not to continue analyzing one by one, let me know, okay?
P.d II: And if after analyzing all this, you still think that the changes you mentioned in your code should be made, let me know. Dale?
P.d III: It was (too) late for me here. Ergo, I’m going to sleep because tomorrow my son comes to visit me. And, precisely for this reason, tomorrow (nor) will I be able to do the tests that I need () () Unless I do them when my son falls asleep or when he leaves, heh.
Therefore, if you wish, you have at least (almost) all day tomorrow to tell me if any of the optimizations that I need to (re)test (since 15), have (or could have) something to do with the problem that gave rise to this thread.
See ya.

Hello Marko. No problem. No. Not so recently. The truth is that I dont remember. But what is certain is that it was a while ago.

The “problem” is that, surely you need to know if it was before or after a certain update of your plugin, right?

Well. If that’s it, I don’t know how to answer you.

In the meantime, I await your comments.

See ya.