Clear Nginx for Webuzo 1.0.1

The Webuzo sidebar now displays Clean Nginx Cache. The plugin name and page heading remain Clean Nginx Cache Wordpress Connector.

Packages:

• Webuzo connector 0.5.9
• Clear Nginx for Webuzo (WordPress) 1.0.0

The WordPress ZIP is identical to the existing 1.0.0 package. Install the Webuzo ZIP through Webuzo Admin → Plugins to get the shorter menu label.

Both installable ZIPs and SHA256SUMS.txt are attached.

Clear Nginx for Webuzo 1.0.0

Packages

• WordPress: Clear Nginx for Webuzo 1.0.0 — clear-nginx-for-webuzo-1.0.0.zip.
• Webuzo: Clean Nginx Cache Wordpress Connector 0.5.8 — webuzo-clean-nginx-0.5.8.zip.

The WordPress plugin clears the hosting account's Nginx cache directly from the toolbar or tools page. The Webuzo companion now uses its new name in the plugin list, menu and page heading.

The README contains the current requirements and installation steps, with the third-party statement at the end. The two plugins have separate version numbers.

Download the two installable ZIPs below. SHA256SUMS.txt verifies both packages.

Webuzo Clean Nginx 0.5.7 + Clear Nginx for Webuzo

Clear Cache in the WordPress toolbar now clears cache directly and returns to the page you were viewing. Settings remains a separate dropdown link.

Changes

• The primary toolbar button submits the existing authorized purge operation using POST and an operation-specific nonce.
• Returns safely to the originating administrator or frontend page. Invalid/external return URLs fall back to the local tools page; non-string return fields are rejected.
• Displays the result on the originating administrator page.
• Replaces the tools-page introduction with: "Clear cached pages to help visitors see your latest changes."
• Removes the enrollment schedule and backend implementation paragraphs from the WordPress tools page. The account-wide warning remains visible.
• Updates translations, documentation and both package versions to 0.5.7.

The Webuzo package updates its version display and bundled documentation. The privileged bridge protocol, native clear command, credentials and ten-minute enrollment cron are unchanged. The existing 0.5.6 companion remains compatible with the 0.5.7 WordPress plugin.

Downloads and installation

• WordPress: clear-nginx-for-webuzo-0.5.7-public-review.zip.
• Webuzo Admin: webuzo-clean-nginx-0.5.7-public-review.zip.
• SHA256SUMS.txt verifies both installable ZIPs.

Use these assets rather than GitHub's Source code archives. Replace the WordPress plugin through the normal plugin upload/update screen and reload the dashboard. Updating the Webuzo companion is optional for this UI change; follow the installation and removal guide when replacing an earlier development installation. Cache clearing continues to affect every website in the hosting account.

Verification

• 124 PHP assertions: 29 native protocol, 41 WordPress client and 54 handler/UI.
• 26 live WordPress HTTP checks on the packaged code, including actual toolbar purges from Dashboard and frontend, return paths, success notice, CSRF/method rejection and other-account cache preservation.
• Full static and runtime Plugin Check scans pass without excluded checks, using separate copies of the WordPress package with all annotation comments removed.
• Full coding standards and PHP compatibility checks pass with the existing, documented single @lstat() metadata-check annotation. This release adds no ignores. See the exact exception and historical validation scope.
• Public source and both ZIPs pass the private-information publication audit.

These are developer-run checks, not an independent penetration test or WordPress.org approval. This remains a review candidate. Earlier releases and their assets are unchanged.

Independent third-party integration; not affiliated with, endorsed, sponsored, or supported by Webuzo or Softaculous.

By Byron Iniotakis. GPL-2.0-or-later.

Webuzo Clean Nginx 0.5.6 + Clear Nginx for Webuzo

Clear Nginx for Webuzo now uses WordPress error/filesystem APIs and identifiers matching its name. Both installable packages are included.

Changes

• Namespace/package ClearNginxForWebuzo and prefix clear_nginx_for_webuzo_ for WordPress actions, operation-specific nonces, notices and error codes.
• Removes old WordPress namespace/action aliases and settings migration. Earlier development forms/nonces are not supported; reload the dashboard after installation.
• Expected client failures return WP_Error, checked with is_wp_error(), with escaping at display time.
• Credential contents use WP_Filesystem_Direct::get_contents(), preserving local Unix permissions without changing global filesystem settings or requesting FTP/SSH credentials.
• Original operation input must match the exact allowed values before sanitize_text_field() is applied. Altered input is rejected.
• The native bridge protocol, Webuzo clear command and ten-minute enrollment cron remain unchanged. The Webuzo package updates its version display and bundled documentation.

Explicit remaining exception

The WordPress source retains one documented phpcs:ignore for native @Lstat() metadata checks. It handles a missing/concurrently removed credential as WP_Error without emitting a raw filesystem-path warning. Full PHPCS with annotations disabled reports that one WordPress-Extra warning. WordPress-Core permits this native function; the plugin keeps the stricter full ruleset with the exception explicitly documented. This is not a claim of zero exceptions or guaranteed reviewer acceptance.

Full Plugin Check static and runtime scans pass without excluded categories. Separate copies with all annotation comments removed also pass Plugin Check.

Install or replace development copies

1. Deactivate the old WordPress development plugin first.
2. In Webuzo Admin > Plugins, deactivate the old Webuzo plugin before deleting its uploaded bundle, so its removal hook can run. For the old service-based candidate this stops/disables its purge service and removes its known installed files. For the native bridge candidate it removes the enrollment cron and revokes credentials.
3. Upload and activate webuzo-clean-nginx-0.5.6-public-review.zip. Open Nginx Cache and confirm version 0.5.6, ready state and enrolled accounts.
4. Install and activate clear-nginx-for-webuzo-0.5.6-public-review.zip in WordPress, reload the dashboard, then test connection and clear cache. Remove inactive earlier WordPress copies through the Plugins screen.

If the separate old purge service was installed without a Webuzo plugin, or its known unit remains, the new activation retires the known old service files after validating them. The exact administrator/root changes and file paths are documented in the installation guide. Do not manually delete account cache folders. Lifecycle installation/removal does not clear websites or cache contents; manually clicking Clear Cache affects all websites in the hosting account.

Verification

• 134 public assertions: 29 native protocol, 41 client, 47 WordPress handler/UI and 17 isolated Linux lifecycle checks.
• 35 actual WordPress HTTP/PHP-FPM assertions with WP_DEBUG=true on two clean installations. Private debug logs contain zero unexpected entries; original configurations are restored byte-for-byte.
• Full Plugin Check 2.1.0 static/runtime scans, plus annotation-free copy scans, pass without excluded checks.
• 22 native administrator-panel lifecycle assertions, eight WordPress 6.0/PHP 7.4 assertions, 15 malformed-input HTTP smoke assertions and 36 final installed-package/host checks.
• Actual Webuzo Nginx Cache screen displays 0.5.6, ready state and enrolled accounts. Original Webuzo core baseline PHP files remain unchanged.
• Public source and both ZIPs pass the private-information publication audit.

These are developer-run checks, not an independent penetration test or WordPress.org approval. This is an independent third-party integration, not affiliated with, endorsed, sponsored, or supported by Webuzo or Softaculous.

Assets

• Webuzo Admin: webuzo-clean-nginx-0.5.6-public-review.zip
• WordPress: clear-nginx-for-webuzo-0.5.6-public-review.zip
• SHA256SUMS.txt verifies both installable ZIPs. GitHub Source code archives are repository snapshots, not individual plugin packages.

Exact installation and removal steps | WordPress quality checks and exception | Security scope

By Byron Iniotakis. GPL-2.0-or-later.

Webuzo Clean Nginx 0.5.5 + Clear Nginx for Webuzo

Fixes the WordPress.org automated submission rejection caused by the WordPress companion's Update URI header.

Changes

• Removes Update URI and uses the standard WordPress update mechanism. There is no custom updater or external update service.
• Removes the redundant explicit translation loader and its Plugin Check suppression. WordPress handles directory translations automatically.
• Adds a package build guard against reintroducing Update URI and updates the readme, changelog and quality report.

The account-scoped protocol, native purge command, permissions and ten-minute enrollment cron are unchanged. The existing 0.5.4 Webuzo companion remains compatible: upgrading only the WordPress plugin is sufficient for this fix, with no credential rotation or server reconfiguration. The 0.5.5 server package changes version metadata and bundled documentation only.

Verification

• Plugin Check 2.1.0: full static and runtime scans pass with no reported errors or warnings and no excluded checks, including plugin_updater.
• WordPress Coding Standards and PHP compatibility checks pass.
• 107 portable assertions pass; Linux lifecycle tests run in the isolated Linux environment.
• 35 actual WordPress HTTP/PHP-FPM checks pass against the unchanged 0.5.4 server companion, including stale content becoming visible after purge and another hosting account retaining its cache.
• Public source and both ZIPs pass the private-information publication audit.

Automated results do not guarantee WordPress.org approval and are not an independent penetration test.

Downloads and submission

• Upload clear-nginx-for-webuzo-0.5.5-public-review.zip for WordPress.org review. Do not upload the server companion or GitHub Source code archives as the WordPress plugin.
• webuzo-clean-nginx-0.5.5-public-review.zip is the companion for hosting administrators.
• SHA256SUMS.txt verifies both ZIPs.

This is an independent third-party integration, not affiliated with, endorsed, sponsored, or supported by Webuzo or Softaculous.

WordPress quality checks | Installation

By Byron Iniotakis. GPL-2.0-or-later.

Webuzo Clean Nginx 0.5.4 + Clear Nginx for Webuzo

The WordPress companion is now Clear Nginx for Webuzo, with the matching folder, main file and text domain clear-nginx-for-webuzo. The native server plugin remains Webuzo Clean Nginx.

Upgrading WordPress

1. Deactivate the previous Webuzo Site Cache plugin first.
2. Install clear-nginx-for-webuzo-0.5.4-public-review.zip and activate Clear Nginx for Webuzo.
3. Use Tools > Clear Nginx for Webuzo > Test connection, then Clear Cache > Clear Cache.
4. Remove the inactive old WordPress copy after verification.

The new bootstrap rejects activation if the previous implementation is still loaded, with explicit upgrade instructions. It does not deactivate any other plugin automatically. Existing account credentials, internal actions and notice identifiers remain compatible. No new general API key or native backend reconfiguration is needed for the rename.

The readmes identify this project as an independent third-party integration, not affiliated with, endorsed, sponsored, or supported by Webuzo or Softaculous.

Verification

• Twelve actual migration assertions: duplicate activation rejected without a fatal class collision, the old plugin remains active after rejection, both accounts manually upgrade successfully, the minimum-version fixture upgrades, and native credentials remain byte-identical.
• 107 portable assertions and 35 real WordPress HTTP/PHP-FPM checks with WP_DEBUG=true, private logs containing zero unexpected entries, and restored original debug settings.
• Eight WordPress 6.0 / PHP 7.4 compatibility assertions and 36 final installed-package/host checks.
• WordPress Coding Standards/PHP compatibility pass. Plugin Check static/runtime scans retain only the documented GitHub Update URI directory exception. This release is not a claim of WordPress.org approval or an independent penetration test.

The account-scoped transport, native clear command and ten-minute enrollment cron are unchanged. The cron never purges cache. A manual clear affects all websites in the hosting account. Original Webuzo core baseline PHP files remain unchanged.

Assets

• WordPress: clear-nginx-for-webuzo-0.5.4-public-review.zip
• Hosting administrator: webuzo-clean-nginx-0.5.4-public-review.zip
• SHA256SUMS.txt verifies both installable ZIPs. GitHub Source code archives are repository snapshots.

Upgrade instructions | WordPress quality checks | Security scope

By Byron Iniotakis. GPL-2.0-or-later.

Webuzo Clean Nginx 0.5.3 - Webuzo + WordPress

Version 0.5.3 addresses WordPress review follow-up items while preserving account-only cache clearing.

Changes

• Temporary administrator notices now use the full webuzo_site_cache_notice_ prefix and remain isolated per user. Older short-prefix notices expire normally; they are not read or migrated.
• The WordPress readme explicitly documents the fixed local Webuzo connection, companion-plugin dependency, signed JSON fields, standard WordPress HTTP User-Agent and data that is not sent by the plugin. No remote executable assets or author analytics are loaded.
• Updated translation template, documentation and regression fixtures.

The Webuzo bridge protocol, native command, signing credentials and ten-minute enrollment schedule are unchanged. The cron never purges cache. A manual purge affects all websites in the hosting account.

Debug-mode verification

The 35 real WordPress administrator HTTP/PHP-FPM checks were rerun on two clean installations with WP_DEBUG=true, private logs outside the webroots and error display disabled. A logging probe confirmed both logs worked. Both logs had zero unexpected entries after functional and Plugin Check runs. Original WordPress configuration files and the prior Plugin Check activation state were restored afterward.

Additional checks passed: 106 portable assertions, a real stored-transient isolation fixture, 8 WordPress 6.0 / PHP 7.4 compatibility assertions and 36 final installed-package/host checks. WordPress Coding Standards and PHP compatibility report zero errors/warnings with documented narrow exceptions. Current HTTP fixtures use WordPress 7.1.4 / PHP 8.3. Original Webuzo core baseline PHP files remain unchanged.

Plugin Check 2.1.0 static and runtime checks pass when excluding only plugin_updater. The full scan retains the documented WordPress.org-specific Update URI finding because this release is distributed through GitHub. This is not a claim of WordPress.org approval or an independent penetration test.

Installable downloads

1. Hosting administrator: deactivate the installed Webuzo plugin, upload webuzo-clean-nginx-0.5.3-public-review.zip in Webuzo Admin > Plugins > Installed Plugins > Add New, then reactivate.
2. WordPress administrator: install/update webuzo-site-cache-0.5.3-public-review.zip and use Tools > Webuzo Site Cache > Test connection.
3. Clear Cache > Clear Cache performs a manual account-wide purge. No general panel API key is needed.

Use the two plugin ZIP assets below. GitHub Source code archives are repository snapshots. SHA256SUMS.txt contains both ZIP checksums.

WordPress quality and debug checks | Installation | Security scope

By Byron Iniotakis. GPL-2.0-or-later.

Webuzo Clean Nginx 0.5.2 - Webuzo + WordPress

Version 0.5.2 updates the WordPress companion to follow WordPress development practices while retaining account-only native cache clearing.

Changes

• WordPress HTTP API replaces the custom socket/HTTP parser. Requests use one fixed loopback URL, no redirects or session cookies, a twenty-second timeout and a bounded response. HMAC validation of exact request/response bytes and account scope remains required.
• Translatable UI and errors, translator comments and a bundled POT template.
• Toolbar CSS is enqueued only for an authorized visible toolbar, with keyboard focus styling.
• Updated plugin/readme metadata, contributor orloxgr, Tested up to 7.1, and an Update URI for GitHub distribution.
• Repeatable Composer/PHPCS checks and documented quality results.

The Webuzo bridge protocol, native command, account isolation and ten-minute enrollment schedule are unchanged. The cron never clears cache. Purging affects all websites in the hosting account.

Verification

• WordPress Coding Standards 3.4.1, PHP_CodeSniffer 3.13.6 and PHPCompatibilityWP 2.1.8: zero errors or warnings with the documented narrow exceptions.
• Plugin Check 2.1.0: static and runtime scans pass when excluding only the WordPress.org-only plugin_updater check. The full scan reports the expected Update URI directory rule; this GitHub release is not a claim of WordPress.org approval.
• 104 portable assertions, 35 actual WordPress administrator HTTP/PHP-FPM checks, 8 minimum-version fixture checks and 36 final installed-package/host checks.
• WordPress 6.0 / PHP 7.4 compatibility fixture; current WordPress 7.1.4 / PHP 8.3 deployment fixture. Original Webuzo core PHP baseline files remain unchanged.

These are developer-run checks, not an independent penetration test or a complete theme/plugin compatibility matrix.

Installable downloads

1. Hosting administrator: deactivate the existing Webuzo plugin, upload webuzo-clean-nginx-0.5.2-public-review.zip in Webuzo Admin > Plugins > Installed Plugins > Add New, then reactivate.
2. WordPress administrator: install/update webuzo-site-cache-0.5.2-public-review.zip and use Tools > Webuzo Site Cache > Test connection.
3. Clear Cache > Clear Cache performs a manual account-wide purge. No general panel API key is needed.

Use the two ZIP assets below; GitHub Source code archives are repository snapshots. SHA256SUMS.txt contains both asset checksums.

WordPress quality checks | Installation | Security scope

By Byron Iniotakis. GPL-2.0-or-later.

Webuzo Clean Nginx 0.5.1 - Webuzo + WordPress

Version 0.5.1 adds automatic account enrollment through a root-owned cron, scheduled every 10 minutes.

Enrollment behavior

• Newly created accounts become available after native Nginx cache/proxy is enabled and the next successful sync.
• The same job discovers cache enabled later on an existing account.
• Existing account keys, nonce history and purge cooldowns are preserved.
• Disabled/deleted accounts lose their enrollment. Recreated account identities get fresh capabilities.
• The cron only reconciles the plugin's registry and credentials. It never clears cache.

The fixed job is installed as /etc/cron.d/webuzo-clean-nginx, with a 45-second timeout and nonblocking lifecycle lock. Busy runs retry at the next scheduled interval. The administrator page displays the last sync. Deactivation removes the job and revokes credentials; a previously queued refresh cannot recreate a disabled installation.

Downloads

1. Webuzo: upload webuzo-clean-nginx-0.5.1-public-review.zip in Admin > Plugins > Installed Plugins > Add New, then activate. Deactivate before replacing an older ZIP, then reactivate.
2. WordPress: upload webuzo-site-cache-0.5.1-public-review.zip, activate, and use Tools > Webuzo Site Cache > Test connection.
3. Use Clear Cache > Clear Cache. Clearing affects all sites in the hosting account.

The assets below are the installable ZIPs. GitHub Source code archives are repository snapshots. Asset checksums are attached as SHA256SUMS.txt.

Verification and requirements

Developer-run checks include a real scheduled enrollment of a new native account, late cache enablement with actual PHP-FPM connectivity, unchanged existing cache files and credentials, deleted-account revocation, cron lifecycle and operation after reboot. The portable suites contain 84 assertions. Existing purge isolation and WordPress behavior remain verified. All 598 original Webuzo PHP baseline files remain unchanged.

The host needs working system cron, Python 3, GNU timeout, a supported Webuzo native backend and isolated hosting UIDs/private groups. The WordPress connection remains limited to status and account purge, with signed requests/responses and no general API key. This is a review candidate, not an independent penetration test. Native command completion does not independently verify every cache deletion.

Installation and root-owned files · Security scope and checks

By Byron Iniotakis. GPL-2.0-or-later.

Webuzo Clean Nginx 0.5.0 - Webuzo + WordPress

Webuzo administrator plugin and companion WordPress plugin, version 0.5.0. Review candidate on the native-panel-bridge branch.

What changed

WordPress now requests Webuzo's native account cache clear through the existing panel backend. The custom root filesystem broker is retired. No separate purge daemon, sudo rule, timer or cron is installed, and no Webuzo core or Nginx/PHP configuration is patched.

Each hosting account receives its own purge-only signing credential outside website directories. Requests and responses use HMAC-SHA256, timestamps, fresh nonces and replay protection. The server chooses the account from its root-only registry; callers cannot choose an account, path or command. Native account creation metadata is checked to reject stale account identities.

Installable downloads

1. Webuzo: upload webuzo-clean-nginx-0.5.0-public-review.zip in Admin > Plugins > Installed Plugins > Add New, then activate.
2. WordPress: upload webuzo-site-cache-0.5.0-public-review.zip, activate, and open Tools > Webuzo Site Cache > Test connection. There are no API settings to paste.
3. Use Clear Cache > Clear Cache in the WordPress toolbar.

Clearing affects all websites in the hosting account. Wait 2 seconds between requests and 10 seconds between clears. Deactivate/reactivate the Webuzo plugin to refresh enrollment or rotate credentials after account changes. No automatic reconciliation cron is included.

When upgrading, deactivate the Webuzo plugin before replacing its ZIP, then reactivate. The WordPress plugin removes old saved API settings on an administrator visit. Revoke any old broad account API key separately in Webuzo; deleting a saved copy does not revoke it.

Use the plugin ZIP assets below. GitHub's automatic Source code archives are repository snapshots. SHA-256 checksums for the two installable assets are attached as SHA256SUMS.txt.

Tested scope and limits

Developer-run checks cover the signed protocol, WordPress client and administrator controls; native two-account isolation; outside-cache symlink fixtures; real WordPress content edit and anonymous HIT-to-MISS behavior; native lifecycle, credential revocation and rotation; bounded native execution; and operation after reboot. All 598 original Webuzo PHP baseline files remain unchanged. These checks are not an independent penetration test.

Tested with Webuzo 4.9.1 on Ubuntu 24.04, panel PHP 7.4 and WordPress PHP 8.3. Requires the existing loopback end-user listener on port 2002, isolated account UIDs/private groups, Python 3 for lifecycle and GNU timeout. The existing panel backend remains privileged. The UI confirms normal native command completion, not an independently verified deletion count. Revalidate after Webuzo upgrades.

Installation and removal · Security scope and checks

By Byron Iniotakis. GPL-2.0-or-later.