Nagaoka Design

<p>This plugin helps WordPress developers by showing which template files are being used on the current page. It displays the current template file name and directory path in a convenient overlay, making it easy to identify which template is rendering the current page during development.</p>
<p>The plugin shows a small, unobtrusive display that can be clicked to reveal detailed information about all template files loaded for the current page.</p>
<p><strong>Key Features:</strong><br />
* Shows current template file name<br />
* Displays template directory path<br />
* Click to view all included template files<br />
* Configurable display position (top-left, top-right, bottom-left, bottom-right)<br />
* Customizable background and text colors<br />
* Admin-only display option for security<br />
* Debug mode option (only shows when WP_DEBUG is enabled)<br />
* Lightweight and performance-optimized<br />
* Clean, modern interface</p>
<p><strong>Perfect for:</strong><br />
* Theme developers<br />
* WordPress developers<br />
* Site debugging<br />
* Template hierarchy understanding<br />
* Development and staging environments</p>
<p>The plugin is designed to be completely safe and non-intrusive, with options to restrict visibility to administrators only.</p>


Current Page Template Viewer

Display current template file and directory name on screen for WordPress development.

Viktor Szépe

<h4>Only for development!</h4>
<h4>Now with OPcache memory consumption support</h4>
<p>This plugin dumps the colorized filenames and memory consumptions or file sizes after the normal WordPress HTML output, after the closing html tag. This generates invalid HTML but gives you an overview of loaded plugins and the current theme.</p>
<p><em>What’s running</em> lists all files parsed and executed by the PHP engine. It can be used for plugin or theme refactoring.</p>
<h4>Now you can highlight your own plugin and theme</h4>
<p>Provide a part of its path in wp-config.php:</p>
<pre><code>define( 'WHATS_RUNNING_HIGHLIGHT', 'wp-content/plugins/my-plugin' ); </code></pre>
<h4>Color codes</h4>
<ul>
<li>your code is highlighted with YELLOW background</li>
<li>plugin files are in BLUE</li>
<li>themes files are in ORANGE</li>
<li>files in the wp-includes directory are in GREEN</li>
<li>files in the wp-admin directory are in GREY</li>
<li>all other files are in RED</li>
<li>VIOLET bar after the filename represents the file size ( 0.5 kB/px )</li>
<li>DARK MAGENTA bar after the filename represents the OPcache memory consumption ( 1 kB/px )</li>
</ul>
<h4>Links</h4>
<p>You can watch <a href="https://core.trac.wordpress.org/ticket/28364" rel="nofollow ugc">WP core bug #28364</a> to get more information about <a href="https://github.com/szepeviktor/WPHW/blob/master/wp-entry-points.md" rel="nofollow ugc">WordPress entry points</a>.</p>
<p>You can find some documentaion here what makes a WordPress plugin efficient: https://github.com/szepeviktor/WPHW</p>
<p>Development of this plugin goes on on <a href="https://github.com/szepeviktor/whats-running" rel="nofollow ugc">GitHub</a>.</p>


What's running

Lists WordPress require() calls mainly for plugin code refactoring.

Current Page Template Viewer vs What's running