| 开发者 | dalibord |
|---|---|
| 更新时间 | 2026年4月28日 16:02 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
?wpcu URL parameter?nowpcu URL parameter<script> and <style> on the page/wp-content/plugins/code-unloaderPHP 8.0 or higher. The plugin will not activate on PHP 7.x.
Yes. Rules are stored in a custom database table and are not affected by caching plugin cache clears.
The kill switch is a one-click emergency recovery button in Settings > Code Unloader > Settings. When active, all rules are bypassed and every asset loads normally. Your rules are not deleted — they resume when you deactivate the kill switch.
Appending ?wpcu to any frontend URL will automatically open the asset panel for logged-in administrators, even on pages where the Admin Toolbar is hidden. The parameter stays in the URL while the panel is open and is removed when you close it.
Appending ?nowpcu to any frontend URL disables all Code Unloader rules for that single request — the page loads exactly as if the plugin were not active. This follows the same convention as ?nowprocket (WP Rocket) and ?ao_noptimize=1 (Autoptimize). Useful for testing, debugging, or performance scanning tools that need to measure the raw unoptimized asset baseline.
Yes. When creating a rule, choose Regular Expression as the match type. Patterns are validated before saving, and a regex warning is shown to help you keep patterns specific.
Inline blocks are <script> and <style> tags that are printed directly into the page HTML rather than being registered through WordPress's enqueue system. The Inline Blocks tab in the panel detects and lists these blocks so you can identify them.
DELETE /groups/{id}) and deleting all groups now purges 3rd-party page cache.phpcs:enable scope corrected in delete_all_groups() so the WordPress.DB.DirectDatabaseQuery.* suppression doesn't leak past the intended block.POST /rules returning 500 (Internal Server Error) when creating rules whose 6-column scope (url_pattern, match_type, asset_handle, asset_type, device_type, group_id) already existed with different condition settings — the in-PHP duplicate check was stricter than the DB UNIQUE KEY, allowing the insert to fall through to a duplicate-key violationPOST /rules/enable with scope: page) threw a TypeError — PatternMatcher::match() was called with the pre-1.5 signatureRuleRepository::find_duplicate() now matches the DB UNIQUE KEY exactly (6-column identity). Conditions are attributes of a rule, not part of its identity — one active rule per (url_pattern, match_type, asset_handle, asset_type, device_type, group_id) scopecu_log.action ENUM in fresh CREATE TABLE now includes group_activate and group_deactivate (matches the migration ALTER)identity_key schema drift on cu_rules (pre-release dev artifact) — drops the orphan column + misaligned UNIQUE KEY and re-adds the correct 6-column composite keysnapshot_key schema drift on cu_group_items — same pattern, different table; collapsed group snapshots to 1 per group, which broke group enable/disable cascade on rulesuniq_rule database index updated to include group_id — the same rule can now correctly exist in multiple groups at the database level (DB version 1.2)code-unloader/ folder — resolves all PCP text domain mismatch false positives caused by wrong folder name