Orpharion
| 开发者 | mt8biz |
|---|---|
| 更新时间 | 2026年5月28日 08:30 |
| PHP版本: | 8.3 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
The
wp_options table accumulates leftovers from plugins and themes that have been deactivated or deleted but never cleaned up. Those rows bloat the autoload payload on every page load and there is no built-in way to decide which ones are safe to remove.
Orpharion observes which options are actually read at runtime, attributes each read to the plugin or theme that caused it, and surfaces the raw signals (accessor, autoload flag, size, last-read timestamp) so administrators can decide what to remove:
- Observe — the tracker records when and by whom each option is read, using the live PHP backtrace to identify the real caller.
- Quarantine — rename the option temporarily so WordPress and the accessing plugin can no longer see it; confirm nothing breaks.
- Delete — the row is removed from both
wp_optionsand the tracking table. Use the Export selected bulk action first if you want a restore copy; Orpharion never writes option_value content to the server filesystem on your behalf (option_value can contain API keys, SMTP credentials, and other secrets that should not leak into backups ofwp-content/).
build/index.js, build/index.css) is published at https://github.com/mt8/orpharion — see the Source code section below for the exact build steps.
安装:
- Upload the plugin directory or install the zip via Plugins → Add New → Upload.
- Activate the plugin.
- Open the Orpharion menu in the WordPress admin sidebar and let the tracker run for a few days before acting on the results.
常见问题:
Is tracking safe to leave on in production?
Yes. Tracking is buffered in memory and flushed once per request at shutdown. A sampling-rate option and a 10-minute activation window triggered by admin traffic keep the overhead predictable.
Will deleting an option break my site?
Use Quarantine first. A quarantined option is renamed, not deleted; if anything breaks you can restore it with one click. Only permanently delete after you have confirmed nothing is broken during the quarantine window.
What happens to my data if I uninstall the plugin?
Uninstalling restores any active quarantines to their original names, drops the custom tracking and quarantine tables, removes plugin-owned options, and clears the scheduled cron job. Your regular wp_options data is untouched.
Where does the name "Orpharion" come from?
The orpharion is a Renaissance plucked-string instrument invented in England in 1581 by John Rose. The name is a 16th-century coinage from Orpheus and Arion, two legendary musicians of Greek mythology. Music by John Dowland, William Byrd, and others was published for it. The plugin borrows the name as a nod to the idea of carefully tuning what sits in your wp_options table.
更新日志:
1.1.4
- Assets: add the square plugin icon (128×128 and 256×256) used by the WordPress.org plugin directory listing and the installed plugins screen. No functional changes.
- readme: the Source code section (public GitHub repository and
npm run buildreproduction steps for the compiled admin bundle) is now placed directly after Description so the build-source pointer is immediately visible. - readme:
Tested up tobumped to 7.0 to reflect the current WordPress release. - Read tracker: plugin and mu-plugin frame classification in
Tracker::classify_trace()now goes throughplugin_basename()instead of comparing againstWP_PLUGIN_DIR/WPMU_PLUGIN_DIRdirectly. This reuses WP core's plugins-root resolution (including symlink awareness via$wp_plugin_paths) without duplicating the constant references in plugin code. Behavior is unchanged for standard setups; the legacymu:slug prefix on mu-plugin readers is dropped (it was not consulted anywhere downstream).
- Admin menu icon: the opacity override is now attached to a registered style handle via
wp_add_inline_style()onadmin_enqueue_scriptsinstead of being printed as an inline<style>tag fromadmin_head. Visual behavior is unchanged. - Read tracker: the
WP_PLUGIN_DIRandWPMU_PLUGIN_DIRreferences used to classify backtrace frames are now routed throughwp_normalize_path(), with a comment recording why those constants are referenced (identifying other plugins' install roots — Orpharion's own location is resolved from__FILE__). - Documentation:
readme.txtnow includes a "Source code" section pointing to the public GitHub repository (https://github.com/mt8/orpharion) and thenpm run buildflow used to regenerate the bundled admin assets.
- WP-CLI:
wp orpharion export --output=<file>now requires a bare*.jsonfilename and always writes intowp-content/uploads/orpharion/. Absolute or relative paths and non-.jsonextensions are rejected so option_value content (which can include API keys, SMTP credentials, and other secrets) cannot be written to a web-accessible location. The export directory is created on demand withindex.htmland.htaccessso it is not browseable.
- Renamed the plugin from "Optrion" to "Orpharion" to remove an external trademark conflict before the WordPress.org review. The slug, text domain, REST namespace, WP-CLI command, internal option keys, hooks, and the quarantine rename prefix all move from
optrion/optrion_toorpharion/orpharion_. There is no in-place migration: this is a one-shot rename done before any wp.org release.
- Consolidated the protected-option rules (WordPress core options, Orpharion's own
orpharion_*namespace, and the quarantine rename namespace) into a singleProtectedOptionshelper. The cleaner, importer, quarantine, and options-list filter now all derive their behavior from that one source of truth, with consistent name normalization across all of them.
- Options list: pick rows per page (25 / 50 / 100 / 200) and jump directly to a page number.
- Options list: the quarantine / export / delete action bar is now also rendered below the table, so you can act on a selection without scrolling back up.
- Hardened the protected-option check to match the storage layer's collation semantics (case-insensitive, trailing whitespace tolerant), so a non-canonical spelling cannot slip past Orpharion's safeguards.
- Hardened the importer to mirror the cleaner's protected-name set: WordPress core options, Orpharion's own internal options (
orpharion_*), and the quarantine rename namespace are skipped instead of being written towp_options. Skipped entries are reported in the import summary and the WP-CLI output.
- Initial public release.
- Per-option read tracking: every
get_option()call is attributed to the real plugin or theme on the PHP backtrace. - Options list with individual signal columns (accessor, autoload, size, last accessed) and inactive-only / autoload-only / accessor-type filters.
- Quarantine workflow with manifest table, automatic expiry (restore / delete / keep), and a still-accessed guard that blocks deletion of options that are still being read.
- No server-side persistence of option_value content: JSON exports are browser downloads only.
- REST API under
/wp-json/orpharion/v1/*(requiresmanage_options). - WP-CLI commands for scripted pipelines, including
--accessor-type,--inactive-only, and--autoload-onlyfilters onlist,export, andclean. - Full Japanese localization.