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.
