v1.2.1

Housekeeping release. No behaviour change in the panel.

Fixed the license

The plugin header has always declared GPL-2.0-or-later while the shipped license file carried the MIT text — which is what GitHub was detecting. The file is now the GPL-2.0 text, renamed LICENSE.

Renamed the plugin directory

The plugin folder and main file were wrt-inspector while the repository was what-renders-this. what-renders-this is now canonical everywhere the outside world sees a name: repository, zip top-level, plugin directory, main file. The wrt_ / WRT_ code prefix is unchanged.

Upgrading from 1.2.0 or earlier: WordPress keys plugins by directory, so this reads as a separate plugin. Install this version, activate it, then delete the old wrt-inspector/ folder.

Added readme.txt

wordpress.org reads readme.txt, not README.md. README.md stays as the GitHub-facing document; both ship in the zip.

Added build.sh

Replaces the copy-paste build block in the README. It refuses to build when the plugin header, WRT_INSPECTOR_VERSION and the readme.txt stable tag disagree, and asserts that the zip contains a single top-level what-renders-this/ directory — a flat zip unpacks loose into wp-content/plugins/ and WordPress will not recognise it as a plugin.

v1.1.0

Works on activation. No constant, no wp-config.php edit, no environment check.

v1.0.0 refused to run unless wp_get_environment_type() returned something other than production. Managed hosts report production for staging and dev installs alike, so the plugin sat dead on exactly the environments it was built for — and the workaround was asking every user to edit wp-config.php.

The environment check was not protecting anything. manage_options is the real boundary: every path the panel prints is already visible to that user in the dashboard, nothing is written to the database, and ACF field values stay off unless requested per request.

Changes

• On by default, everywhere. WRT_INSPECTOR is now an opt-out: define('WRT_INSPECTOR', false);
• New wrt_inspector_enabled filter for conditional control (per environment, per user, per URL).
• Sends nocache_headers() when the gate passes, so a misconfigured full-page cache cannot store an administrator's response and serve the panel to anonymous visitors.

Upgrade by replacing the plugin folder. If you added define('WRT_INSPECTOR', true); for v1.0.0, it stays valid — it is now redundant.

v1.0.0

Dev-only page inspector for WordPress. On any frontend page it reports the resolved template file, the route and post context, the attached ACF field groups, and the ordered chain of theme partials that fired.

Install — download wrt-inspector.zip below, then Plugins → Add New → Upload Plugin.

Enable it — the plugin runs only for manage_options users on a non-production environment. Managed hosts often report production from wp_get_environment_type() even on staging, so set the constant explicitly in wp-config.php:

define('WRT_INSPECTOR', true);

The same constant set to false is a hard off switch.

Notes

• Partials are listed in first-inclusion order. get_included_files() is unique-per-file, so a partial pulled in by several modules appears once, at its first position.
• ACF field values are opt-in per request via ?wrt-inspect-values=1 and are not fetched server-side otherwise.
• ?wrt-inspect=1 opens the panel without the admin bar.
• Not yet verified against a live WP Engine staging install.