atutrabajo

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 explain:

Yesterday I told you that…

…”little by little I am solving some things that may have caused this and other problems”…

In this sense, you should know that, in my “zeal” (someone would say obsession, heh:), to optimize my site, I had read (among the thousands of things I read because I don’t understand ANYTHING about this, heh), that could you add to my function.php some code like this;

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 had NOT reappeared. 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.

And guess what. Exact. So far, the errors have NOT reoccurred. Except one which is, unfortunately, the following (As always I will replace my user and my site with; myuser/mysite, heh)…

…”[Fri Jan 27 11:12:50.541874 2023] [:error] [pid 1547091:tid 47495644215040] [remote 66.249.77.135: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”…

What is the good new? That those IDs are NOT MINE, heh.

Let me explain: This site is still under development and, therefore, I finish doing something, I test, correct, test again and so on.

And one of the (many) tests I do is, of course, the performance tests on Pagespeed.

Ergo. If those IDs are NOT mine, then they must be one of the many that Pagespeed uses to “simulate” its tests, right?

That is why, probably, what you told me about that…

…”I can’t replicate the problem“…

Because, precisely, the problem is NOT generated by my site, but by Pagespeed, testing my site, 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, please reconsider the instructions you sent me from the beginning

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.

P.d I: While I was writing this, I kept testing things and, as in the Pagespeed tests I did, it happened to me that the images (just the “metie” of your plugin), seemed to me that they took longer than before to load (enable) the function 9) (Disable image scaling) and 12) (Eliminate JS enqueued in the header and take it to the footer) I re-enabled these functions and, later, I did the test in question again in Pagespeed. And guess what. Exact. The “problem” with your plugin Gone!

Ergo, these are the UPDATED functions installed in my function.php, plus their corresponding “explanation”;

https://docs.google.com/document/d/1lLtll3o27OOVbPHQfcoL7n7z3m-GlxTe/edit?usp=sharing&ouid=102851233358919075037&rtpof=true&sd=true

What does this mean? (I think, heh).

a) That some of the functions that had been installed caused the problem that your plugin “generated”.

b) That some of the functions that are below the line that says…

Until here (Day I)

They cause the problem and because of that, I was still getting ONLY the error generated by your plugin.

c) That the problem was NOT generated by any of the optimizations above that line. But when removing those indicated as 9) and 12) the problem generated by the optimizations below that line reappeared.

Whatever. 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 Arya. Yes. Now I remember you (It happens that I am “fighting” with several plugin developers at the same time, heh). Anyway.

Having said that:

I read what you posted in the previous thread. But you must understand that you are talking to a “simple” Administration Graduate who understands NOTHING about Programming (and who also hates it, heh).

However, because I know I need to do this and (for now) I can’t pay someone else to do it, I’m slowly fixing a few things that may have caused this and other problems.

When I’m done, I’ll get to yours and I’ll tell you, okay?

See ya!

Thanks Mark.

I await your comments.

Regards.

P.d: I will never get tired of pointing out that you are one of the (few) plugin developers who attend in a timely manner (as befits, heh). For that, again, thank you.

Hello Marko. Thanks for answering.

Yes. Of course…

• I use PHP Version 8.1.13 (Compatible with 64bit)

Plus…

• I have installed the latest version of WordPress (6.1.1)

Do you need any other information?

I await your comments.

Thanks, again.

Regards.

Dear / os. Hello. First of all, thanks for answering. Although, having said that…
I’m sorry I wasted so much time SPOTLY describing each and every error that is generated EXCLUSIVELY when your plugin is ACTIVATED.
Anyway. One way or another, let’s get started…
1) Regarding:
…”Often, we see problems occur in combination with another plugin or theme. The quickest way to rule out any conflicts is to disable all non-Yoast plugins and switch to a standard theme like Twenty Twenty”…
I want to tell you that I HAVE ALREADY DONE ALL of this, so it’s a kind of “standard procedure” that I ALWAYS use. Even BEFORE contacting the plugin developers.
And of course, AFTER trying ALL of that, the problem persists ONLY when Yoast Seo is enabled.
By the way, the latest standard theme that’s out there is Twenty Twenty Three, heh. () () Which shows that this spitch is standardized for EVERYONE. Anyway.

2) Regarding:
…”Try it on your development or staging site, if you have one. Otherwise, we recommend using the Health Check & Troubleshooting plugin (https://www.ads-software.com/plugins/health-check/). This plugin has a troubleshooting mode, which does not affect normal visitors to your site”…
I tell you that I am doing these tests, precisely, in a development site, heh.
Also, I did not know about Healt Ckeck but, as I told you when I opened this ticket… It is NOT necessary!
Why? Simple. Because the ONLY problems were already DETAILED for them.
For example:
In /home/myuser/mysite/wp-includes/plugin.php(205): WP_Hook->apply_filters() says;
$filtered = $wp_filter[ $hook_name ]->apply_filters( $value, $args );
That is to say;
Either you should have mentioned in the code of your plugin what WordPress says or WordPress should have put in that line, what you say.
It’s that simple, heh.

3) In relation to:
…”If you are not familiar with checking for conflicts, we would like to point you to a step-by-step guide that will walk you through the process: How to Check for Plugin Conflicts (https://yoast.com/help/how-to-check- for-plugin-conflicts/)”…
The same applies here as in points 1) and 2)

Finally, obviously that of…
…”If you are not comfortable doing it yourself or if this does not solve your problem, our Yoast SEO Premium plugin (https://yoast.com/wordpress/plugins/seo/) comes with one year of (technical) support”…
It is ABSOLUTELY RULED OUT (at least for now and until my site is sustainable).
But also, your proposal even has a certain “whiff” of “blackmail.” Mhmm. Anyway.

In any case, and even if I decided on that “solution”, who assures me that the code of the Premium version does not have the SAME problems?

So, please, could you send the necessary update/s to adapt the code of your plugin in such a way that the previously described errors are corrected?

From already thank you very much.

Regards.

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

Ups. No sabía que era bueno hacer esto, je. En fin. Todos los días se aprende algo nuevo.

Es más, en rigor de verdad, nunca lo hice antes, je (*)

(*) Cuando se resolvía, solo agradecía y listo,

De hecho, ni siquiera sabía como se hacía (*)

(*) Pero ahora veo que, acá abajo (en inglés), dice “Responder y marcar como resuelto”.

Bueno. De nuevo, gracias. Y ahora lo marco como resuelto.

Saludos.

Hola Krystle. Gracias (de nuevo) por responder.

Respecto de…

“tocar un campo de entrada” es que la petición se activa cuando plataforma (el navegador + sistema operativo) detecta un campo de formulario que espera una entrada (un texto, número, fecha o similar)”…

Francamente NO tenía idea. Gracias por la aclaración pues, recién ahora entiendo (aunque de programación NO sé nada, je:).

Dicho esto, quería avisarte que, lisa y llanamente… ?Sos una GENIA!

Acabo de instalar en mi function.php el código que me propusiste y ?tanaaan!…

https://ibb.co/3c91G44

Como podés ver, la llamada en cuestión ?Ya NO aparece!

Francamente no sé como crearon ese código pero, te juro que ?hace casi 1 semana que estoy buscando algo así!

De nuevo, gracias.

Saludos.

PD: Respecto a TODO lo demás y, en cuanto a WebPageTest, francamente (como ya mencioné), perdí TODA esperanza de que alguna vez me contesten, je.

Ergo. Si alguno de Uds. tiene contacto con ellos, sería bueno que les avisen y/o que, por lo menos, hagan pública esta solución pues, estoy seguro que, a más de uno le debe estar pasando algo parecido.

De un modo u otro, de nuevo, gracias por tu tiempo.

Nos vemos.

Ok Gijo.

So, I will assume that, there is NO solution on your part for this problem.

Anyway, I thank you.

Greetings.

I understand.

But see if this helps:

From the Elementor debug report, the following error comes up…

strtolower(): Passing null to parameter #1 ($string) of type string is deprecated

And, going back to the topic of the “keywords” that you mentioned earlier, the ones in the “problematic” files (and that I loaded in your plugin) are the following:

frontend.min.js

webpack.runtime.min.js

frontend-modules.min.js

ALL, of course, belonging to Elementor.

So, with all this background… can you think of any solution?

I await your comments.

Thanks.`

Hola Krystle. Antes que nada, gracias por responder. Dicho esto…

1) Si. Sé que que es un …”problema específico de la plataforma WebPageTest”…

2) NO tengo idea de que es “tocar un campo de entrada” ni (mucho menos) que es un “dispositivo LineageOS (una distribución de Android).

3) Además, siempre lo realizo desde mi Pc y, ese archivo, me empezó a aparecer hace poco. Es decir, antes NO estaba.

4) Vi el enlace que me enviaste (Y también lo había visto antes, je). Y, aunque de programación NO entiendo NADA, veo que, al final del mismo dice algo así como que…

…”vaya si eran difíciles de aislar! Una vez más me confirmaron en mi decisión de cortar mis lazos con Google. Me inundaron las entradas en PCAPDroid de todo tipo de aplicaciones y servicios de Google, además de Wiko bloat”…

Algo que yo NO me puedo dar el “lujo” pues, como dije, no tengo fucking idea.

Con respecto a si…”?probaste quitando Google Analitycs”… Si. Ya probé, je.

Ergo. Lo único que me queda es ver como hago para EVITAR esa llamada desde mi sitio.

Porque, si bien es cierto que, como dices…

…”es un problema específico de WebPageTest”…

También lo es que, si te fijas en los informes, hay como un “vacío” de unos cuantos milisegundos, entre el archivo anterior y el que le sigue a googleapis.

Esto, en mi modesto entender, implica que, esta “llamada de porquería”, si bien no se ve reflejada en otras herramientas, es como que “estira” la carga de la página.

Y, lo que es peor. Ni siquiera se deja “cachear” (Por eso aparece en WebPageTest sin ningún tilde. Ni del caché de mi sitio ni el de Cloudflare).

Ergo. Si no lo resuelvo, siempre va a seguir “estirando” la carga de mi sitio.

?Alguna otra solución?

Aguardo tus comentarios.

Saludos.

P.D: También estuve averiguando una alguna función y/o comando para bloquear las llamadas externas, pero solo encontré esta…

Usar los siguientes comandos de wp-config.php:
define(‘WP_HTTP_BLOCK_EXTERNAL’, true)
define(‘WP_ACCESSIBLE_HOSTS’, ‘*.www.ads-software.com, .mywebsite.com, .peticion3.com, peticion4.com, peticionN.com’)

Pero esto me dejaría el problema de que NO sé que peticiones si tendría que autorizar.

Ergo ?Tenés o se te ocurre algo mejor?

Ergo. Lo más probable es

Hi Gijo. First of all, thanks for replying. Having said that…
Indeed, you are right. That’s why I mentioned that…”ONLY 3 files were incompatible”…
And I took the trouble to copy the content of those 3 files.

That is, when those 3 files are NOT inside your plugin, everything works Ok.
But when I add THOSE keywords (as you call them) Boom! Elementor editor stops working.

Please, considering the above…
Could you check the content of those 3 javascript files and see if there isn’t any incompatibility with your plugin?

From already thank you very much.

Greetings.

Hello. No problem. As we say around here…”better late than never”…heh!
But, since you are. I have another problem with your plugin that I hope you can help me solve.
I explain:
As we have already seen, the “problem” was that my caching plugin (W3TC) was compressing your plugin’s css file, called wp-content/uploads/dynamic-mobmenu.css
Ergo. What I did was, exclude said file from the minimized one and soooo! The problem was solved.
But…
When I remove it from the minimize process, what happens is that Google Pagespeed informs me that I should…
…”Remove resources blocking rendering”…
And the ONLY file it mentions is wp-content/uploads/dynamic-mobmenu.css
The “curious” thing is that this notice is NOT always given. And also, NOT on all pages.
But ALWAYS it happens, it does it with – for example – this page;
https://stage9.atutrabajo.org/curriculum-vitae/
I understand that it is a “giant” page, heh (When I finish it, it will have “barely”, +45 thousand words, heh!).
Maybe that’s why Google Pagespeed warns me that I should do “something” with that file and, as I said, on that page.
One way or another, I ask you…
Do you have any code or something that makes the file in question load deferred (defer) or asynchronous (async)?
I could go into your plugin code and look it up myself, ha! But I understand that the next time you update the plugin, everything will go back to the way it was.
So, I would prefer you to tell me if, by means of – for example – some function to insert in my child theme’s function.php, I could “convert” the file in question (dynamic.mobmenu.css) into an asynchronous file and/or to load lazy.
I await your comments.
From already thank you very much.
Greetings.

Hello. As “promised is debt”, a thousand apologies for not having contacted me before, heh.
Anyway. Having said that…
– On the one hand, I wanted to congratulate you because, as I had already told you, the searches on the site, plus the code you sent me (to “match” ga=galite) are working, as you can see in the following screenshot , https://ibb.co/ZBrSkGp
– On the other hand, ask you if there is any way to include in these reports, the searches that do NOT include information related to the pages or articles that I already have.
I’ll explain…
In the tests I did, I put words in the search engine that I know have nothing to do with my site. For example: candy, heh!
Why? Well, precisely because I would be interested in knowing what my visitors are looking for and what I still don’t have on my site.
Obviously, I am NOT going to dedicate myself to selling candy, heh. But I would have liked the word candy to appear in the report.
If you can’t, it doesn’t matter. We leave everything as it is and, we assume that, in one way or another, we are collaborating with the visitor, by making the visit faster. Something that, on the other hand, I myself appreciate when I visit other sites.
In other words, let’s settle that the matter is resolved and we close the case.
But, if possible, I would like to know how, so that someday (if a word has many searches), I could start focusing my next articles around that word.
Back. If you can’t, no problem. I had a hard time configuring everything as it is.
And, as I told you before, the cost of a change should be less than its benefit, heh.
One way or another, thanks for the plugin, for your input, and for your patience.
See you.

Hello (again, heh:). I have to apologize to you because, after sending you my previous comment, I proceeded (as I mentioned) to;
1) Unlink Ajax Search Lite from Google Analitycs
2) Remove from Analitycs the ajax-search parameter
However.
When I went to my Analitycs (to remove the aforementioned parameter), I found this;
https://ibb.co/8rdkFD2
In other words, as you can see, your recommendations YES. They worked!
What happened is that these results were only seen the next day (and NOT in a couple of hours, as you say in your article, heh:)
Having said that, it seems that searches are reflected like any other event, but NOT immediately (ie in the “live traffic window”, as you mentioned in a previous thread).
So if – apparently – your plugin + the script you sent me… THEY WORK!
As for the “error” you mention, I THINK it has to do with the fact that the script that loads GALite is async
That is…
<script async src=”/wp-content/uploads/external/gal.js”></script>
And at the same time, my caching plugin (W3TC) was combining it and… adding “defer” to it! ??
Anyway.
I just added the file in question (the one that runs GALite on my site) to the W3TC minified (and combined) “exceptions” list, but it’s “taking” a long time to finish “cleaning” it of all the source code. .
Which leads me to “suspect” that, despite the fact that, as you say, said error appears immediately after loading GALite, apparently it has NOT to do with said script! (But with someone else) (*)
Anyway, I already tried everything again (after excepting the js file mentioned above) and apparently it works ok (That is, the code loads, the “stuff” is seen in my Analitycs, it does NOT block me from loading the site , etc.).
But, as I mentioned, in the source code, you still see the “combination” of that file (external/gal.js) as async and – at the same time – defer, heh.
Okay. I have already reintegrated your tool with my Google Analitycs as I had previously described.
I’m going to keep trying to do test searches in your search engine and tomorrow I’ll tell you the results.
For now that’s all.
Thank you very much and, again, a thousand apologies.
Greetings.
PS: (*) Update:
1) Indeed, the only code that looks like that is the Facebook pixel!
<!– Facebook Pixel Code –>
<script>async defer crossorigin=”anonymous”
‘/wp-content/uploads/external/fb.js’;
fbq(‘init’, ‘xxxxxxxxxxxxxxxxxx’);
fbq(‘track’, ‘PageView’);
</script>
Therefore, I removed the GALite one from the exceptions, and added this one.
2) Anyway, in my source code, the “error” you mention still appears because, strictly speaking, if you look closely, it is part of the “construction” of the Facebook pixel insertion function.
This is…”<script>async defer crossorigin=”anonymous”
But, as you surely know, this code is the one that “offers” Facebook itself, to insert its pixel.
3) So, I leave it as it is and remove the script file for said pixel from the W3TC minify / merge exclusions.
In any case, I still don’t know very well what I’m installing said pixel for, because I just “informed” that they NO LONGER have Analitycs!
Anyway, as it does NOT bother me (it does not block the loading of the site) for now I leave it.
Later I will see if I can hire a FB Marketing specialist (Community Manager) and see if he finds any use for it. Or, I will proceed directly to delete it.
Okay. For now that’s all. I’ll keep doing search tests (with and without sense for my site) to see what results my Analitycs registers.
I’ll tell you tomorrow.

Bueh. by telling me…
…”If you decide to switch to the original Google Analytics code, it is very likely that it will start working without problems”…
It means you’re NOT sooo sure, heh.
One way or another, I tell you that I ALREADY tried!
Although, strictly speaking, what I did, as soon as your 1st came to me. The answer, related to this, was to change the GALite code to the “normal” GA code. But frankly, I tried it after a while and did NOT wait for “after a couple of hours” as you mention in your article.
I tried it after about an hour and, since it didn’t work, I left everything as it was, because what IS for sure is what I mentioned in this thread and that is…
…”The “normal” GA code blocks the loading of the page and slows it down”…
And, what I also commented on that…
…”What sense does it make that I can measure well if, when the visitor wants to see one of my pages or posts, it takes a long time to load”…
Anyway.
If at any time you have any “integral” solution for this, I would like to be among the 1st. to find out
If not it does not matter.
In the meantime, I am going to unlink your plugin from my Analitycs because, although the integration between both tools does NOT work, what I am sure of is that NOTHING is free!
In other words, surely, even if it does NOT work, the “communication” between both tools generates some kind of “delay” on my page.
For now that’s all.
Anyway, thanks (for the plugin and for your time).
Greetings.