Kirtikumar Solanki

Nexora Site Toolkit centralizes useful site information and admin workflows in one place. It is designed for administrators who want a clear picture of their site without browsing the server filesystem.
Overview — WordPress, PHP, MySQL, database size, disk space, theme, plugins, SSL, locale, and URLs.
Content — Posts, pages, media, comments, categories, tags, and users by role.
Server & PHP — Server software, PHP extensions, object cache, REST API status, cron events, and registered image sizes.
Security — Read-only checks for SSL, file editor lock, debug mode, administrator count, and more.
Shortcuts — Quick links to native WordPress admin screens (Dashboard, Site Health, Media, Plugins, etc.).
Tools — Copy or download a plain-text site report; maintenance checklist; refresh uploads size cache.
My Nest — Private admin notes saved to your user account in WordPress (not files on disk).
Settings — Dashboard widget, admin bar link, default tab, pinned shortcuts, and uploads cache duration.
This plugin does not provide a file manager. It does not browse, upload, download, edit, rename, or delete files on the server.
Only users with the <code>manage_options</code> capability can access the toolkit.

Nexora Site Toolkit

Your WordPress admin command nest — environment stats, content metrics, security checks, shortcuts, and private notes. No file manager.

loonpwn

Whoops error handling, no password logins, template hints, no indexing, flush rewrites, everything a developer needs for their local development environment.
Components
<ul>
<li>Disallow Indexing Turn off the public blog option. This will modify the robots.txt generation to block all search engines</li>
<li>Flush Rewrites No more weird redirection problems when working on custom post types or taxonomies.</li>
<li>No Password Logins Just stick the user in you want to login as, write anything in the password field, and it will login! Only works when connecting from local host</li>
<li>Whoops Error Handling The error screen from laravel, now in your WordPress setup</li>
<li>Template Hints See which templates are loading for the page you are on</li>
</ul>
The goal is to exchange security for ease of use, for that reason it’s important that you take the security measures needed 
to ensure that someone can’t take advantage of the site with this plugin enabled.
If you’re running on a staging environment ensure you have setup a <a href="http://www.htaccesstools.com/htpasswd-generator/" rel="nofollow ugc">htpasswd</a>
<h4>Filters</h4>
Set Environment
<pre><code>development-environment/is-development
</code></pre>
Dynamically set how the plugin detects if the environment is development based on your own criteria.
Stop a component from loading
<pre><code>development-environment/require-component-$component
</code></pre>
Disable require of a component if you don’t want to use it. Possible values are:
<pre><code>disallow-indexing, `flush-rewrites`, `no-password-logins`, `whoops-error-handling`
</code></pre>

Development Environment

- quote from user -

"When an error is thrown it's so easy to find it and quickly debug why it happened, and the no password login makes my day so much easier 

No More Headaches!

Whoops error handling, no password logins, template hints, no indexing, flush rewrites, everything a developer needs for their local development envir …

Nexora Site Toolkit vs Development Environment