Static Cache Wrangler
| 开发者 | derickschaefer |
|---|---|
| 更新时间 | 2025年11月12日 11:33 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.8 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Static Cache Wrangler is a lightweight, low‑resource static site generator and HTML export engine for WordPress. It automatically creates self‑contained, URL‑agnostic static pages of your site — perfect for anyone who needs to preserve, distribute, or accelerate WordPress content.
Originally developed as a command‑line tool for WP‑CLI, it has evolved into composable, zero‑impact tooling that supports administrators, developers, and site owners alike. Whether you're archiving a client project, deploying to a CDN, or creating a portable offline version that runs anywhere, Static Cache Wrangler delivers fast, CDN‑ready HTML output without complex setup.
Technically, the plugin uses an asynchronous, lazy‑loading build mechanism that generates static pages as visitors browse your site. Over time, your entire site is exported as lightweight static HTML.\
An upcoming free companion plugin will add real‑time build monitoring and manually triggered full‑site generation for any uncached pages.
Unlike traditional static‑site plugins that require full crawls or database schema changes, Static Cache Wrangler is zero‑impact:
- Does not add custom database tables or modify your schema
- Automatically cleans up all plugin options, cron jobs, and transients upon uninstall
- Keeps your WordPress database completely untouched
- Runs all caching processes asynchronously in the background
- Offers an optional performance profiler for granular resource and execution insights Perfect for:
- Creating fully offline or portable copies of WordPress sites
- Rsyncing to read‑only Nginx failover servers for high availability
- Publishing WordPress content to Amazon S3®, Netlify®, or other static CDNs
- Geo‑distributing static HTML for ultra‑fast global reads
- Archiving, demos, and secure client deliverables
- Small to mid‑sized sites (≈ 100 pages +) — upcoming assistant plugin expands this to 1 K pages
- Multisite administrators needing scalable static‑cache exports Static Cache Wrangler turns WordPress into a fast, secure, and portable static‑site generator — with no database changes, no vendor lock‑in, and no maintenance overhead.
- Triggering of page rendering requires 1-2MB of PHP memory for the duration of the process.
- Average processing duration is less than 500 ms (meaning memory consumption is quickly released)
- Average asset (JS, CSS, image) batch processing is less than 100 ms
- WordPress Core and theme rendering is generally 20-25 MB; SCW usage keeps total memory below 30 MB
- CLI commands are even more efficient Funding Model
- This plugin and all companion plugins will remain 100% free (true WordPress style)
- Want to make a donation? Consider purchasing a copy of the author's book on command-line interfaces for yourself or as a gift. https://moderncli.dev
- Enable static site generation using the toggle in the sidebar.
- As users browse your site normally, each page visit creates a static HTML file.
- Assets (CSS, JS, images, fonts) are automatically are queued and asyncronously downloaded and localized.
- Processing happens in the background and can be paused anytime.
- Download the complete static site as a ZIP file.
- Extract and open
index.htmlin any browser — it works completely offline.
- Prefix standardization – All template variables, global references, and filters now use the
stcw_prefix, satisfying the latest WordPress.org code scanning rules. - Improved code validation – Passes 100% of the new “Check Plugin” API scan results.
- Updated inline documentation – Improved code clarity and compliance annotations.
stcw_before_file_save— Fires immediately before a static file is written to disk.- Parameters:
$static_file(string) — Path to the file being saved. - Use Case: Start timers, collect memory data, or monitor disk operations before file write.
stcw_after_file_save— Fires after a static file is successfully written.- Parameters:
$success(bool) — True on success.\$static_file(string) — The saved file path. - Use Case: Log, validate, or post-process generated static files.
stcw_before_asset_download— Allows inspection or modification of asset URLs before download.- Parameters:
$url(string) — The original asset URL. - Returns: Filtered URL string.
stcw_after_asset_download— Executes after each asset download completes.- Parameters:
$dest(string) — Destination path.\$url(string) — Original URL. - Returns: Filtered destination path (optional).
stcw_before_asset_batch— Fires before an asynchronous asset download batch begins.- Use Case: Initialize timers or resource tracking for async performance measurement.
stcw_after_asset_batch— Fires after each asynchronous asset batch completes.- Parameters:
$processed(int) — Number of assets processed successfully.\$failed(int) — Number of failed downloads. - Use Case: Record async batch performance, memory usage, or queue diagnostics.
/tools/ directory has been added to the plugin to organize optional developer resources.\
It currently includes:
performance-profiler.txt— A detailed guide describing how to install and use the optional Performance Profiler MU plugin for advanced benchmarking.
- Compliance with 2025 WordPress.org plugin repository standards.
- New developer hooks for performance profiling and async instrumentation.
- Added
/tools/performance-profiler.txtdeveloper documentation. - No behavioral or UI changes for end users.
- Zero database impact — profiling features remain opt-in and inactive by default.
stcw_remove_wp_head_tags and stcw_process_static_html) enable companion plugins and custom integrations, opening up possibilities for agencies, developers, and SaaS providers to extend the plugin without modifying core code.
- Lazy-load static generation — creates static pages only when visited, minimizing CPU and memory usage.
- Automatic asset localization — CSS, JS, images, and fonts are downloaded and referenced locally.
- Relative path rewriting — ensures portability for offline or CDN hosting.
- Zero-configuration — works instantly after activation.
- Zero database impact — does not create or modify any database tables.
- Clean uninstall — all options, transients, and cron events are removed automatically.
- Background processing — non-blocking, low-impact generation.
- One-click export — download a ZIP of the entire static site.
- Modern UI — intuitive, card-based dashboard.
- WP-CLI Support — manage generation, status, cleanup, and export directly from the terminal.
- Clean HTML Output - Removes 7+ WordPress meta tags for portable, framework-agnostic static files
- Developer Hooks - Two extensibility hooks for companion plugins and custom integrations
- Enhanced Security - WordPress version and internal metadata hidden from static exports
- Optimized Performance - 3.1% smaller files and 2.3% faster generation than previous versions
wp scw enable– Enable static generationwp scw disable– Disable static generationwp scw status– View current status and statisticswp scw process– Process all pending assetswp scw clear– Remove all generated static fileswp scw zip– Create a ZIP archive of the site
安装:
- Upload the plugin files to
/wp-content/plugins/static-cache-wrangler/or install via Plugins > Add New. - Activate the plugin from the Plugins screen.
- Navigate to Settings → Static Cache to enable generation.
- Browse your site normally — pages are cached as they load.
- Click Download ZIP to export the complete static version.
屏幕截图:
常见问题:
Does it work with any theme or builder?
Yes — Static Cache Wrangler captures the final rendered HTML, so it works with any theme, builder, or framework (Elementor®, Divi®, Gutenberg®, etc.).
Does it use a lot of resources?
No — it's designed as a lazy loader, generating static pages only on demand with minimal memory and CPU impact.
Does it modify my database?
No — it never alters your WordPress database schema or adds tables.\ All plugin-related options, transients, and scheduled events are automatically removed upon uninstall.
Can I use the exported site on any server?
Absolutely. The output is plain HTML and assets — deploy it on any web server, CDN, or open it directly in a browser.
Does it handle dynamic content?
Dynamic features like forms, comments, or live feeds won't function in the static version, but all rendered content and assets are preserved exactly.
How do I update after making changes?
Revisit the updated pages while generation is enabled, or run wp scw process to rebuild all static content.
Can I customize the configuration?
Yes! You can customize file locations and behavior using constants in wp-config.php:
Change static files location:
define('STCW_STATIC_DIR', WP_CONTENT_DIR . '/my-static-files/');
Change assets location:
define('STCW_ASSETS_DIR', WP_CONTENT_DIR . '/my-assets/');
Disable async asset processing (process immediately):
define('STCW_ASYNC_ASSETS', false);
What if I need advanced customization?
You can use WordPress filters to customize behavior:
Exclude specific URLs from generation:
add_filter('stcw_should_generate', function($should, $url) { if (strpos($url, '/private/') !== false) { return false; } return $should; }, 10, 2);
Modify HTML before saving:
add_filter('stcw_before_save_html', function($html) { return str_replace('</body>', '<footer>Generated: ' . date('Y-m-d') . '</footer></body>', $html); });
What WordPress meta tags are removed in version 2.0.5?
Version 2.0.5 removes the following WordPress-specific meta tags from static HTML:
- RSD (Really Simple Discovery) links for XML-RPC
- Windows Live Writer manifest links
- WordPress shortlink tags
- Generator meta tags (WordPress version)
- REST API discovery links
- oEmbed discovery links
- REST API HTTP headers
data-wp-strategyattributes on script tags These tags serve no purpose in static sites and removing them improves portability and security.
How do I use the new developer hooks?
Remove additional WordPress tags:
add_action('stcw_remove_wp_head_tags', function() { remove_action('wp_head', 'your_custom_action'); });
Modify HTML before saving:
add_filter('stcw_process_static_html', function($html) { // Add custom footer, remove tracking, etc. return $html; });
See the plugin documentation for 15+ complete examples.
Do I need to regenerate my static files after upgrading?
No, but it's recommended. Existing static files will continue to work, but regenerating will give you the cleanest output with all WordPress meta tags removed:
wp scw clear
wp scw enable
Then browse your site to regenerate pages.
Can I create companion plugins for Static Cache Wrangler?
Yes! Version 2.0.5 introduces two hooks specifically designed for companion plugins:
stcw_remove_wp_head_tags- Remove additional WordPress tagsstcw_process_static_html- Modify final HTML output These enable agencies, developers, and SaaS providers to build specialized extensions without modifying core plugin code.
Will this work with my SEO plugin?
Yes! Version 2.0.5 is fully compatible with:
- Yoast SEO
- Rank Math
- All in One SEO Pack
- SEOPress
- The SEO Framework The meta tag removal only affects WordPress core tags, not SEO plugin meta tags that contain important information.
更新日志:
2.0.6
- WordPress.org Compliance Release – “Moving Goal Post”
- Version 2.0.6 is a WordPress.org compliance update ensuring full compatibility with the latest repository validation standards introduced in 2025
- Implemented prefix standardization – all template variables, global references, and filters now use the
stcw_prefix for WordPress.NamingConventions.PrefixAllGlobals compliance - Achieved 100% pass on the updated “Check Plugin” API validation scans
- Enhanced namespace isolation and improved code safety for plugin interoperability
- Improved inline documentation for better code clarity and compliance traceability
- Developer Enhancements
- Introduced new developer hooks to support the forthcoming Static Cache Wrangler Performance Profiler MU plugin
- Added foundations for advanced performance profiling and benchmarking via WP‑CLI integration
- Enhanced developer experience with cleaner structure for extending cache behavior
- Improvements
- Non‑functional update focused on long‑term maintainability and ecosystem compliance
- Verified adherence to current WordPress.org repository and coding‑standards checks
- Refined internal structure to support future diagnostic and profiling modules
- Compatibility
- Tested with WordPress 6.8.3 and PHP 7.4 – 8.3
- Fully backward compatible with 2.0.5
- Migration Notes
- No functional changes to caching logic
- Recommended: Regenerate static files after update for clean metadata
- Enhanced Static HTML Output
- Implemented hybrid WordPress meta tag removal using native
remove_action()with regex safety net - Removed 7+ WordPress-specific meta tags from static output (RSD, wlwmanifest, shortlinks, generator, REST API, oEmbed discovery)
- Stripped
data-wp-strategyattributes from script tags for cleaner HTML - Reduced HTML file size by 3.1% and generation time by 2.3%
- Improved security by hiding WordPress version information from static exports
- New Developer Hooks
- Added
stcw_remove_wp_head_tagsaction hook - remove additional WordPress head tags before generation - Added
stcw_process_static_htmlfilter hook - modify HTML output before saving to file - Added
STCW_Generator::remove_wordpress_meta_tags()method for centralized tag removal - Improvements
- Enhanced code documentation with comprehensive PHPDoc comments
- Better extensibility for companion plugins and theme integration
- Follows WordPress coding standards and best practices
- More maintainable code with clear separation of concerns
- Compatibility
- Tested with WordPress 6.8.3
- Compatible with PHP 7.4, 8.0, 8.1, 8.2, 8.3
- Works with all major themes, page builders, and SEO plugins
- Migration Notes
- No breaking changes - fully backward compatible with 2.0.4
- Recommended: Clear and regenerate static files for cleanest output (
wp scw clear && wp scw enable) - Optional: Review new hooks for customization opportunities
- Major WordPress.org Compliance & Refactor Release\ This update brings the plugin fully in line with current WordPress.org Plugin Directory requirements and coding standards. Nearly every internal file, reference, and namespace was audited, renamed, or rewritten for long-term maintainability and compliance.
- Plugin slug, text domain, and directory renamed from
static-cache-generator→static-cache-wranglerto meet naming and trademark guidelines. - All file, class, and function prefixes updated from
STCG→STCWfor consistent 4-character namespace compliance. - Text domain and translation calls unified across all PHP files for proper i18n validation.
- Folder structure and includes modernized for autoloading consistency and WP.org scanning compatibility.
- Admin interface and view templates refactored for cleaner markup and translation readiness.
- CLI namespace and command base confirmed as
scw(formerlyscg) with backward compatibility removed for clarity. - All GitHub and asset references updated to reflect the new canonical project name and repository.
- Packaging and distribution scripts updated for compliance (clean
.zipexports excluding dev files). - BREAKING CHANGE: Sites upgrading from earlier builds must deactivate the old “Static Cache Generator” plugin, delete it, and install/activate “Static Cache Wrangler.” Data and generated files can be safely regenerated once activated.
- WordPress.org Compliance Update
- Changed all PHP prefixes from SCG_ to STCW_ (4+ character requirement)
- Properly enqueued all scripts and styles (removed inline code)
- Extracted CSS to admin/css/admin-style.css
- Extracted JavaScript to admin/js/admin-script.js and includes/js/auto-process.js
- WP-CLI commands unchanged for user convenience (still
wp scw) - BREAKING CHANGE: Requires clearing and regenerating static files after update
- All option names changed (scw_enabled → stcw_enabled, etc.)
- All WordPress hooks changed (scw_process_assets → stcw_process_assets, etc.)
- See full migration guide on GitHub for technical details
- Enhanced stability and performance
- Improved CLI feedback and logging
- Refined asset handling and path rewriting
- Clean uninstall now clears all options, transients, and cron events
- Minor UI and accessibility improvements
- Complete rewrite with modern coding standards
- WP_Filesystem support for all operations
- Stronger security and sanitization
- Modern admin UI with real-time asset tracking
- Full WP-CLI integration
- Fixed Plugin Check and PHPCS compliance
- Initial release