Rate project ideas for all Wordpress users — "Bugs for Wordpress"?

With each page load, Wordpress runs pretty much all kinds of code. There download plugins and themes, etc., etc.
In any link of the chain may have different problems that lead to complete failure of the pages, or, for example, to load more slowly.

All failures can be viewed through the Apache log file. All right. Except for one problem: they can not see through it.

Therefore, in all these cases you have to manually search the site by "debug logging" to add many file_put_contents in wp-settings (usually the problem) until you can establish a narrow specific area.
In this case, if the load is large, then there is confusion from different queries.
And even then you need to remove it all to not slow the server and haven't filled the disk.

The project "Bugs for Wordpress" - it patches the files to wp-settings, wp-load, maybe some others.
The project will follow all updates of Wordpress, so it is always current patches.

Each "bug" is in fact an advanced version of the file_put_contents, which is in the file divides the code into sections. But heavily modified.
First of all, of course, all the "bugs" can time on / off.
Also, all measurement of performance. Allows, for example, to determine what in order to work faster, this you need not to upgrade the processor and hard drive, replace it with SSD. But in other case
it would seem that similar - you need to configure the DBMS, inhibits it, and the disk is fast enough.
And yet, for example, in the case of an error in the plugin you can find out exactly where in the plugin file, this error - to fix it yourself without waiting for the developer of the plugin (register_shutdown_function).

Similar things can be done for other CMS.
June 10th 19 at 14:45
3 answers
June 10th 19 at 14:47
What is there to evaluate? Dumb idea to do all through f**, which suggests that you are poorly guided in the development of PHP and especially WordPress. No offense, but this bike level Intern / junior developer early. For any higher level this idea sounds at least strange.
The idea to introduce a similar debug in the engine - custom.
You crapped all over it. However, no alternative offered.
Now after this review you have something to offer (if not completely inadequate).
But it will be the answer such: now to get xdebug, that's what the Apache logs, but for this, take such a Profiler, and that's what so-and-so plugin put, etc. - in short every server spend your precious time on installing and configuring the heap of bodies instead of installing a Tula in a couple of clicks, and the result will be that even all this "gang" of "bodies" know not all that may be able to run this option for example on shared hosting everything is not "take". - allen_Davis49 commented on June 10th 19 at 14:50
June 10th 19 at 14:49
You're welcome.
And to thank and for what. The answer at random from the Amateur.
1. Not all the bugs he catches. I even checked, although it was clear that will not get caught.
Register_shutdown_function need it. Or both.
2. And secondly, and foremost, the question is not about how to catch the error - it the theme broader. Themselves and r_s_f and try-catch is useless if you stupidly shove it in wp-load or index (as in the top file) - it will be a little confused, need a system that will understand the context, you may automatically make some decisions to rectify the problem, like to disable the plugin. But this is already necessary described "bugs". - allen_Davis49 commented on June 10th 19 at 14:52
June 10th 19 at 14:51
A Query Monitor will not help in this situation?
Clearly, there are similar plugins, but the functionality of all plug-ins are more limited than the "injection", which loaded before, and will see more. - allen_Davis49 commented on June 10th 19 at 14:54
alas, but I cannot imagine a case in which I would dare to patch the kernel for debugging and profiling. - allen_Davis49 commented on June 10th 19 at 14:57

Find more questions by tags WordPress