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".

Marcus (aka @msykes)

Marcus

Pixelite

WP Safe Mode allows you to view your site temporarily with certain plugins disabled/enabled as well as switching to another theme.
This is particularly useful if you are experiencing problems with a specific plugin or theme and need troubleshoot without it affecting the rest of your site visitors.
Additionally, a loader file can be directly installed via FTP to help you access an inaccessible site due to PHP errors (e.g. blank screens or white screen of death) to help restore it from the admin panel.
<h4>Main Features</h4>
<ul>
<li>Enter Safe Mode for just yourself whilst logged in.</li>
<li>Enable Safe Mode for the whole site.</li>
<li>Admin Bar shortcuts for enabling/disabling Safe Mode.</li>
<li>Restrict Safe Mode to certain IP addresses.</li>
<li>Automatic installation (if file permissions allow).</li>
<li>Fallback to a default WordPress theme or one of your choice in Safe Mode.</li>
<li>Prevent or allow Must-Use plugins from loading in Safe-Mode.</li>
<li>Handy loader file via FTP when your site is completely inaccessible.</li>
<li>MultiSite Support
<ul>
<li>Network-wide Safe Mode (for just you, or everyone)</li>
<li>Restrict Network-wide Safe Mode to certain IP address</li>
</ul>
</li>
<li>MultiSite Site-Specific Safe Modes
<ul>
<li>Override Network-wide Safe Mode settings for an individual site</li>
<li>Network Admins can deactivate Network-Active and Must-Use plugins.</li>
<li>Allow individual site admins from enabling safe mode for their own site.</li>
</ul>
</li>
</ul>
<h4>Data Privacy and GDPR Compliance</h4>
No personal data is used or stored by this plugin. For those entering user-only mode, a cookie is loaded to identify that user.

WP Safe Mode

Disable plugins or switch themes for just you or the whole site for debugging, troubleshooting or accessing and restoring a broken website.

Hagakure – Yet Another Error Reporter vs WP Safe Mode