Fumiki Takahashi

TAROSKY INC.

Kunoichi INC

Have you ever seen an error log like the one below?
<blockquote>
PHP Fatal error: Allowed memory size of xxxxxx bytes exhausted (tried to allocate xxx bytes) in /var/www/wordpress/wp-includes/wp-db.php on line 2007
</blockquote>
This means that <a href="https://www.php.net/manual/en/ini.core.php#ini.memory-limit" rel="nofollow ugc">PHP memory limit</a> is exhausted while retrieving data from a database. In any case, this happens when your site has big data and makes insane loops inside.
But we want to know that which plugin tried to retrieve data?
Hagakure adds extra information to error.log file when <code>wp-db.php</code> causes memory limit error:
<pre>[08-May-2019 10:28:37 UTC] wpdb Error Backtrace:
#1 Kunoichi\Hagakure\DbLogger->filter_query() /app/public/wp-includes/class-wp-hook.php Line 286
#2 WP_Hook->apply_filters() /app/public/wp-includes/plugin.php Line 208
#3 apply_filters /app/public/wp-includes/wp-db.php Line 1871
#4 wpdb->query() /app/public/wp-includes/wp-db.php Line 2579
#5 wpdb->get_results() /app/public/wp-includes/class-wp-query.php Line 2979
#6 WP_Query->get_posts() /app/public/wp-includes/class-wp-query.php Line 3387
#7 WP_Query->query() /app/public/wp-includes/post.php Line 1961
#8 get_posts /app/public/wp-content/plugins/hagakure/hagakure.php Line 34
#9 {closure} /app/public/wp-includes/class-wp-hook.php Line 286
#10 WP_Hook->apply_filters() /app/public/wp-includes/class-wp-hook.php Line 310
#11 WP_Hook->do_action() /app/public/wp-includes/plugin.php Line 465
#12 do_action /app/public/wp-includes/template-loader.php Line 13
#13 require_once /app/public/wp-blog-header.php Line 19
#14 require /app/public/index.php Line 17
#15 URI: /?p=1</pre>
This log will always follow the memory limit Fatal Error by <code>wp-db.php</code>. Now you can find <code>#8</code> calls <code>get_posts</code> repeatedly.
We recommend watching logs with notification services like <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/WhatIsCloudWatchLogs.html" rel="nofollow ugc">CloudWatch Logs</a>. 
This error occurs in the productional environment, and you may not have a chance to see it occurs. 
We use Hagakure with our <a href="https://hosting.kunoichiwp.com/" rel="nofollow ugc">hosting service</a>, please look forward to seeing <a href="https://kunoichiwp.com/blog" rel="nofollow ugc">our blog published</a> and describing the integration!
This plugin also adds debug backtrace to error logs. To modify the error level to a detailed backtrace, define the constant in <code>wp-config.php</code> or somewhere else:
<pre>define( 'HAGAKURE_ERROR_LEVEL', E_NOTICE | E_USER_WARNING | E_WARNING | E_USER_ERROR );</pre>
Besides that, if <code>SAVEQUERIES</code> is set <code>true</code>, the slow query log will be logged with PHP debug backtrace. This helps you to debug.
<h3>Acknowledgements</h3>
The base text for dummy content is “Three Ghost Story” by Charles Dickens. The text file is modified the one of <a href="https://www.gutenberg.org/ebooks/1289" rel="nofollow ugc">Project Gutenberg</a>.

Hagakure – Yet Another Error Reporter

This plugin makes it easy to find the root cause of PHP Fatal error: Allowed memory size of xxxxxx bytes exhausted error. AWESOME.


Great

Looks good

A WordPress plugin to clarify meaningless errors like "Allowed memory size of xxxxxxxx bytes exhausted".

Roy Orbitson

<a href="https://www.adminer.org/" rel="nofollow ugc">Adminer</a> is a database administration tool that allows viewing and editing of databases tables, routines, triggers, etc. It also allows running SQL statements to import data, make bulk changes, or perform other complex operations. It is similar in function to phpMyAdmin. It is intended for use by developers and those who have had experience with databases.
This plugin provides a secure connection to your WordPress database, limited to that which is saved in your WordPress configuration, and access is granted only to logged-in accounts that possess the <code>edit_plugins</code> capability (normally admins). This ensures it can only used by those who already have enough privilege to pose a risk to the installation. Each and every request to Adminer will first be authenticated using your WordPress session. Some security plugins impose extra restrictions on admin sessions, so this plugin may not work if you have one installed.
Note that any other databases on the same host and protected by the same credentials will also be accessible in Adminer. This is how databases operate and not a limitation of Adminer nor this plugin. If other databases need different access restrictions, they should have separate credentials.
It comes with all the themes published in Adminer’s Git repository, so you can select a style that suits you.

Database Access with Adminer

Secure and themed, just what I need. Of course I keep this plugin disabled, and only activate when I need to debug something. As an extra protection =)

Themed!

Provides a secure interface to your WordPress database using Adminer, the popular database administration tool.

Hagakure – Yet Another Error Reporter vs Database Access with Adminer