@ottovolts
I read it twice, and I still didn’t really come away with the feeling of having a “fix” for core dump files. It appears to me, just a reiteration of general information (that is already available to anyone with a web browser – from multiple sources), and statements of opinion, rather than results.
In fact, I see a large portions of content in your article that appears to be pretty much “boiler plate” information, if you will.
It would be nice to see some actual test data, some names of plugins you found to be problematic, and perhaps an elaboration on the process of core dump file analysis.
“These files can be of different sizes and usually do not contain useful information to Carry out a debug to identify the problem and eliminate it.”
It would have been interesting of you had taken the time to qualify that statement.
I think this informaiton could be way too general an assertion to be of any practical use to anyone;
“A final recommendation to the plugins programmers.
Before asking for donations with PayPal for your product, make sure it was well written and is really good.
Of rubbish we do not need. We love WordPress because is fast and very well coded, so, why you code a rogue plugin and ask money”
Hmmm. Those are some thought provoking statements, but unfortunately, they aren’t of much use, in my opinion.
“…long investigation on all plugins, we have found a solution about core dump files created by PHP…”
I would have felt much better about reading the article if it contained some actual data from your analysis to support any of your recommendations, opinons, or conclusions , but I didn’t see any of that – beyond the OOB suggestions for trouble shooting, of course. But still, an interesting read, for many reasons.
