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).
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.
Giles_Luettgen18 answered on June 10th 19 at 14:49