TSO Swiss Knife – Advanced Maintenance & Developer Toolkit

Description

TSO Swiss Knife gives WordPress developers and site administrators a single, well-organised panel (under Tools › TSO Swiss Knife) to inspect and control the internal systems that affect performance, stability, and security.

Included modules

  • Activity History — Central log of changes across all plugin tools (options edited, database replacements, maintenance mode, admin menu, and more). Pinned as the default favorite for quick access.
  • Hidden WordPress Profiles — Apply quick presets and toggle safe performance, content, and privacy constants via JSON under the plugin uploads folder (no wp-config.php editing). Runtime filters apply on the next request.
  • Cron Manager — List scheduled WP-Cron events, run or delete non-core hooks, and keep WordPress core cron events read-only (no manual Run / Edit / Delete).
  • Action Scheduler — Inspect WooCommerce Action Scheduler tables, pending actions, and queue health when the library is present.
  • Debug Mode — One-click Developer mode preset for staging (WP_DEBUG, WP_DEBUG_LOG, SAVEQUERIES; errors hidden from visitors), saved as JSON under wp-content/uploads/tso-swiss-knife-advanced-maintenance-developer-toolkit/config/. The tab shows the constants currently in effect (read-only) and copy-paste wp-config.php snippets. Constants already defined in wp-config.php cannot be overridden.
  • Options Editor — Search, inspect, edit, and safely delete wp_options rows with core options protected.
  • Meta Editor — Browse and edit post and user meta. Without an object ID, search matches meta keys only (not values).
  • Option Library — Save named option presets and re-apply them across environments.
  • Export/Import TSO Configuration — Back up and restore selected plugin wp_options settings as JSON (Redirects, Staging Mode switches, Login Protect, Slow Query settings, and more). Does not include Debug/Security JSON under uploads, the Staging mail log, sandbox sessions, or the Slow Query log.
  • Transients — Filter by status and purge expired or all transients in bulk (site transients on multisite require a network/super admin).
  • WP Constants — Read-only overview of relevant constants grouped by category.
  • WP Internals — Inspect post types, taxonomies, roles, query vars, rewrite tags, and shortcodes.
  • REST API Controls — Disable anonymous REST API access or block individual namespaces.
  • Heartbeat Controls — Set Heartbeat mode (default / disable frontend / disable editor / disable all) and interval.
  • Update Manager — Review pending core, plugin, and theme updates, optionally block update checks (staging), and control update email notifications.
  • Slow Query Monitor — Log slow database queries when SAVEQUERIES is enabled, inspect live queries for the current request, export CSV/JSON, and open a summary from the admin bar.
  • Search & Replace — Run dry-run or live serialized-safe search and replace across database tables.
  • Hooks Inspector — Browse the live $wp_filter global, with callback details and a real-time search filter.
  • Rewrite Rules Flush — Soft or hard flush with a single click; search within the current rules table.
  • Server Files Review — Scan for unexpected PHP files in uploads and other writable directories; optionally save robots.txt / .htaccess when you confirm.
  • Redirects — Manage safe redirect rules stored in the database with import and export support.
  • Custom 404 Page — Assign a WordPress page as the site 404 response while keeping the original URL and a real HTTP 404 status (no redirect).
  • Slug Manager — Bulk-edit post and term slugs with conflict detection.
  • Health Report — Compact checks for risky settings, logs, 404 noise, and related issues; download HTML/JSON in the plugin UI language.
  • Reorder & Hide Sidebar — Drag to reorder WordPress admin menu items, rename labels, nest items under another section, or hide items for all admins.
  • Users & Sessions — Review administrators, role-less users, old accounts, and active sessions.
  • Roles & Capabilities — Compare roles, apply capability templates, and audit dangerous caps.
  • Media Cleaner — Review unattached media, missing attachment files, and unreferenced uploads.
  • Uploads Disk Footprint — Scan the uploads folder for size and file-type footprint statistics.
  • Image Sizes Audit — Review registered image sizes and disable unused sizes where appropriate.
  • Security Review — Highlight common hardening and update issues.
  • Core File Integrity — Verify WordPress core files against official checksums and flag unexpected changes.
  • Login Protection — Custom login URL, brute-force limits, and related hardening controls.
  • Comment Anti-Spam — Local honeypot/rate-limit rules plus optional reputation or cloud checks (off until you enable them and add keys where required).
  • Email Diagnostics — Inspect wp_mail settings and send a test email.
  • Staging Mode — For test copies only (all off by default): red STAGING admin-bar label, ask search engines not to list this copy (without changing Settings Reading), hold outbound email, pause WP-Cron execution, and keep a short administrator-only mail log in the database (CSV export). Turn everything off before copying the database back to production.
  • URL & HTTPS Doctor — Explain whether the saved Home and Site addresses still match https, www, and how you opened the admin. Optional one-click loopback check of this site’s own home URL (redirects are not followed), and an optional count of leftover http:// copies of that address. Does not change the database.
  • Server & Runtime — Read-only view of PHP limits, object-cache drop-in, other wp-content drop-ins, must-use plugins, and optional OPcache reset when the host allows it.
  • Content Audit — Find hidden content issues such as empty titles, missing thumbnails, long slugs, and broken shortcodes.
  • Maintenance Mode — Toggle a 503 maintenance page with a custom message and IP whitelist.
  • Plugin Sandbox — Isolate plugin conflicts via a must-use loader: only your selected plugins load for your admin session.

Translations

  • On Tools › TSO Swiss Knife, administrators can switch the plugin UI to Catalan (CAT), Spanish (ES), or English (ENG) without changing the site-wide language.
  • The same choice applies to this plugin’s AJAX responses and admin downloads (for example Health Report HTML/JSON and URL Doctor messages). It does not change the rest of wp-admin.
  • Further locales can be contributed via Translate WordPress once the plugin is published.

External services

This plugin can optionally contact third-party services. None of these calls run unless a site administrator enables the related feature and, where required, provides an API key.

Comment Antispam (optional)

When Comment Antispam reputation or cloud checks are enabled, visitor data from comments or protected contact forms may be sent as follows:

  • Stop Forum Spam (https://api.stopforumspam.org/api) — Used to look up whether an IP, email address, or username has been reported as spam. Sent on each checked submission (results may be cached briefly). Service: Stop Forum Spam. Terms of use · Privacy policy.
  • AbuseIPDB (https://api.abuseipdb.com/api/v2/check) — Used to check IP reputation. Sends the visitor IP and your AbuseIPDB API key (request header). Service: AbuseIPDB. Terms of use · Privacy policy.
  • CleanTalk (https://moderate.cleantalk.org/api2.0) — Used for cloud spam filtering when CleanTalk mode is selected. Sends your CleanTalk access key plus sender email, IP, nickname, URL, message content, and post/page context. Service: CleanTalk. Terms of use and privacy policy.
  • Project Honey Pot (HTTP:BL) — Optional DNS-based IP reputation lookup using your HTTP:BL access key and the visitor IPv4 address. Service: Project Honey Pot. Terms of use · Privacy policy.
  • Akismet — When cloud mode is set to Akismet and the Akismet plugin is active, spam checks are handled by Akismet according to its own settings and policies. Service: Akismet. Terms of service · Privacy policy.

Core File Integrity (optional)

When you run a core integrity scan, the plugin requests official WordPress core checksums from https://api.wordpress.org/core/checksums/1.0/. Only the WordPress version and locale are sent (no personal data). Service: WordPress.org. Privacy policy.

Update Manager language packs (optional)

When an administrator clicks Install pending translations on the Update Manager tab, WordPress downloads language packs from https://api.wordpress.org/translations/ (via core Language_Pack_Upgrader). Locale and package metadata for pending translations are sent; no personal visitor data. This does not run automatically. Service: WordPress.org. Privacy policy.

URL & HTTPS Doctor (optional)

When you click Check this site, the plugin requests this site’s own home URL through the WordPress HTTP API (a loopback, similar to Site Health). Redirects are not followed. No third-party host is contacted and no personal data is sent. The request only runs after an administrator clicks the button.

Health Report security headers (optional)

Opening Health Report (or downloading its HTML/JSON) may request this site’s own home URL with a HEAD request to list common security response headers. Results are cached briefly. No third-party host is contacted and no personal data is sent.

Screenshots

Blocks

This plugin provides 1 block.

  • Tsosk Url

Installation

  1. Upload the tso-swiss-knife-advanced-maintenance-developer-toolkit folder to /wp-content/plugins/, or use Plugins › Add New › Upload Plugin with the ZIP.
  2. Activate the plugin via Plugins › Installed Plugins.
  3. Navigate to Tools › TSO Swiss Knife.

FAQ

Does this plugin work with object-cache plugins like Redis?

Yes. Features that use WordPress cache APIs (for example flushing related caches after cleanup tools) call core functions such as wp_cache_flush() / wp_cache_delete(), which delegate to whatever persistent object-cache drop-in is active (Redis, Memcached, etc.).

Is it safe to delete an option from the Options Editor tab?

The module protects a list of known WordPress core options. For third-party options, verify in your code or database that they are truly unused before deleting.

Does enabling Maintenance Mode block the admin?

No. Logged-in administrators are always bypassed, regardless of IP whitelist settings.

Can I run multiple plugin-testing tools at once?

Use only the Plugin Sandbox in this plugin. Combining it with other per-user plugin override tools may produce unpredictable results.

Does Update Manager change WordPress auto-updates?

No. Automatic updates are managed only by WordPress core (Dashboard Updates). Update Manager can block update checks on staging sites, hide specific plugin updates, and control update email notifications — it does not write auto_update_* site options or hook auto_update_* filters.

When should I use Staging Mode?

Use it on a cloned / staging / local copy, right after you copy the live site, and before you place test orders or browse as a customer. Enable only the switches you need (badge, noindex, hold email, pause cron, mail log). Turn them all off before you copy that database back to production. Do not leave Staging Mode options enabled on the live site.

Does Staging Mode change Settings Reading (“Discourage search engines”)?

No. It adds noindex headers, pauses XML sitemaps, and adjusts robots.txt while the option is on. It does not filter or save blog_public, so opening Settings Reading will not permanently lock “Discourage search engines” after you turn Staging Mode off.

Does Staging Mode send customer emails from a test copy?

Not if you enable Do not send real emails. WordPress still thinks the mail was accepted, but it never leaves the server. A short copy (recipient, subject, excerpt) is stored in the WordPress database for administrators only (not as a public file under uploads). All Staging Mode switches are off until you turn them on.

Does pausing scheduled tasks in Staging Mode delete cron events?

No. Due events stay in Cron Manager but are not executed while that Staging Mode option is on. Turn it off on the live site so reminders and queues run again.

Does URL & HTTPS Doctor change my site address?

No. It only explains mismatches (http vs https, www, folder, and constants locked in wp-config.php). The leftover-http count is also read-only. Use Search & Replace if you decide to rewrite stored URLs, after a backup — always run preview first.

Can I manually run WordPress core cron events?

No. Core hooks (for example wp_version_check or wp_maybe_auto_update) are read-only in Cron Manager: Run, Edit, and Delete are blocked in the UI and in AJAX.

What does Export/Import TSO Configuration include?

Selected plugin settings stored in wp_options (Redirects, Staging Mode switches, Login Protect, Comment Anti-Spam, Slow Query settings, Health alerts, and similar). It does not include Debug/Security/Hidden Profiles JSON under uploads, sandbox sessions, the Staging mail log, or the Slow Query log. Import overwrites the sections you choose; always export a backup first. Login Protect never imports an enabled custom login URL (to avoid lockouts). If Staging switches arrive enabled, confirm you are on a test site.

Does the CAT / ES / ENG language switcher affect downloads and AJAX?

Yes for this plugin. Health Report HTML/JSON, URL Doctor messages, and other TSO AJAX/admin-post responses follow the language selected on Tools › TSO Swiss Knife. The rest of WordPress admin keeps the site language.

Where does the plugin write files?

Runtime config and other managed files go under wp-content/uploads/tso-swiss-knife-advanced-maintenance-developer-toolkit/. The Staging Mode mail log is stored in the database (not under uploads). The Plugin Sandbox may install a must-use loader under mu-plugins (via the WordPress Filesystem API) so early plugin filtering can run; that loader is removed when no sandbox sessions remain. The plugin does not write wp-content/debug.log or edit wp-config.php.

Does this plugin edit wp-config.php?

No. Debug flags, security constants, and hidden-profile toggles are saved as JSON under wp-content/uploads/tso-swiss-knife-advanced-maintenance-developer-toolkit/config/ and applied at runtime. Constants already defined in wp-config.php always take precedence and cannot be overridden from the plugin.

Does Debug Mode create or manage wp-content/debug.log?

No. Debug Mode does not create, truncate, or rotate wp-content/debug.log. Enabling Developer mode only stores JSON flags (WP_DEBUG, WP_DEBUG_LOG, SAVEQUERIES, and related) in the plugin uploads config folder; WordPress or the server then writes debug.log as usual if logging is on. The Debug tab can list and preview common log paths when they already exist. Empty and shrink actions apply only to logs the plugin owns under wp-content/uploads/tso-swiss-knife-advanced-maintenance-developer-toolkit/ — never to wp-content/debug.log.

Is debug.log safe to leave on a live site?

Not by default. With WP_DEBUG_LOG set to true, WordPress writes wp-content/debug.log, which is inside the web root under a predictable name. Depending on your server it may be downloadable by URL, and it can contain absolute server paths, SQL queries and, occasionally, credentials or tokens printed by other plugins. This plugin cannot move the log outside the web root: it only saves WP_DEBUG_LOG as true/false, and a log path must be defined in wp-config.php before plugins load. Recommended: use Developer mode only on staging, block direct access to debug.log at the server level (Apache/nginx rule), or set define( 'WP_DEBUG_LOG', '/path/outside/webroot/debug.log' ); in wp-config.php. Delete or empty the file when you finish debugging. The plugin’s own protected folder under uploads (.htaccess deny rules) does not cover wp-content/debug.log.

Can Server Files write robots.txt or .htaccess?

Yes, but only when you explicitly save from the Server Files Review module. It can write robots.txt and .htaccess at the site or WordPress root — not under wp-content/uploads/. Always review the generated content before saving on production.

Who should use Search & Replace or the Options Editor?

These tools are intended for experienced administrators and developers. Always run Search & Replace as a dry-run first and keep a database backup. In Options Editor, core options are protected, but deleting or editing third-party options can break plugins or themes. When in doubt, export a snapshot or test on staging.

Does Comment Antispam send data to third parties?

Only when you enable reputation or cloud checks and, where required, provide API keys. See the External services section above for each provider, what data is sent, and links to their terms and privacy policies. With all cloud features off, checks run locally (honeypot, rate limits, keyword rules, and similar).

Why do I see two copies of this plugin after installing?

That usually means the ZIP folder name was wrong (for example …-main from a GitHub download instead of tso-swiss-knife-advanced-maintenance-developer-toolkit). Remove the duplicate folder under wp-content/plugins/, keep only the folder whose name matches the plugin slug, and reactivate.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“TSO Swiss Knife – Advanced Maintenance & Developer Toolkit” is open source software. The following people have contributed to this plugin.

Contributors

Changelog

1.1.0

  • Slow Query Monitor: redesigned admin-bar item (severity dot, count pills, sectioned submenu, compact SQL with full text on hover); the slow-query log, live counters and duplicate detection now all ignore queries fired by the admin bar itself; fixed singular/plural wording.
  • Security: capped the number of outbound-link URLs the public View Counter beacon will track, and fixed Staging Mode mail log CSV formula injection.
  • Fixed: Database Search & Replace infinite loop, regex preview mismatch and serialized-object corruption.
  • Fixed: Redirects wildcard loop detection, Content Audit shortcode removal stripping block backslashes, Admin Menu rules hitting the wrong plugin page, robots.txt “Allow: /” override, Image Sizes Audit core-size validation, and leftover legacy .php flag files.
  • Fixed: several View Counter issues (table upgrade on admin_init, import sources, CSV in Excel, timezone date range, mobile overflow); added a 7/15/30-day summary email period and persistent import results; removed the unused “Keep daily detail for” setting.
  • Removed an unused module file (File Footprint).
  • Docs: FAQ explains that debug.log lives inside the web root (wp-content/debug.log), what it can leak, and how to block it or move it outside the web root via wp-config.php.

1.0.9

  • New: View Counter module. Counts post, page and outbound-link-click visits with a small front-end beacon, so counting keeps working even behind a full-page cache (LiteSpeed, etc.). No cookies — de-duplication uses a short-lived, server-side fingerprint only. Adds a “TSO Views” column (with icon) to the Posts/Pages list, sortable by total views, and an importer for totals previously collected by Post Views Counter, WP-PostViews or WP Statistics (WP Statistics’ real per-day history is preserved; the other two only expose a lifetime total, so that one lands dated today). Includes a Top Content report (most viewed posts/pages and most clicked outbound links, filterable by period), a CSV export of the daily detail, and an optional weekly summary email.
  • Security: real-time email alert when a new Administrator account is created or a user is promoted to Administrator, including the IP address and how the request reached WordPress (normal admin form vs. a silent REST/AJAX/XML-RPC request) — the same pattern seen in real-world “hidden rogue admin” incidents caused by a compromised browser extension.
  • Security: Application Passwords audit — lists every active Application Password site-wide with its owner, name, creation and last-used dates and last IP, with per-item and “Revoke All” buttons, since these survive deletion of the user account that created them.
  • Security: added “Application Passwords” and “Recent administrator accounts” checks to the Security Checks table, plus an informational notice explaining that a compromised browser extension can act with a logged-in admin’s session without touching the server, which is outside any WordPress plugin’s control.
  • Security: new “PHP Execution in Uploads” test and one-click protection — probes whether the server executes PHP files placed inside wp-content/uploads (the single control that most often stops an arbitrary-file-upload exploit from becoming a full takeover) and can write the blocking rule into wp-content/uploads/.htaccess on Apache/LiteSpeed.
  • Security: detects administrator accounts that share their exact creation timestamp with another user — a known technique some malware uses to hide a rogue admin from “sort users by newest”.
  • File Integrity: now also scans wp-content/uploads for files with an executable script extension (.php, .phtml, .phar…), since uploads should only ever contain media/data and this is exactly where file-upload exploits drop their payload.
  • REST API: added an option to block anonymous access to /wp-json/wp/v2/users specifically (user enumeration), without disabling the rest of the wp/v2 namespace that the Block Editor needs.
  • Fixed slow queries flagged by Query Monitor: Login Protect and Admin Menu settings options are now autoloaded (both are read on every request/admin screen), instead of triggering a dedicated DB query each time. Existing installs are migrated automatically.
  • Security fix: Login Protect’s custom login URL could be revealed to a logged-out visitor on the first request to any wp-admin page, since WordPress core’s own redirect used the same filtered login URL. Direct /wp-admin/ access is now blocked for logged-out visitors before that redirect can happen.
  • Fixed: the REST API namespace-blocking option could also block an unrelated namespace that happened to start with the same text (e.g. blocking “foo/v1” also blocked “foo/v10”).
  • Security: the “user promoted to Administrator” alert now also fires when a role is added via WP_User::add_role(), not only via the classic role-change dropdown.

1.0.8

  • Admin Menu: the menu manifest (previously an uncached direct DB query on every admin screen) is now cached via the standard WP object cache, compatible with any persistent object-cache backend (Redis, Memcached, LiteSpeed object cache).

Older versions: see changelog.txt in the plugin folder.