Bouzin Fresh Reset

A fresh WordPress start, with strict safety checks.

Bouzin Fresh Reset guides an administrator through an irreversible reset of a supported single-site WordPress installation. It obtains and verifies official WordPress core files, prepares a protected recovery workflow, and preserves the selected administrator account and its existing password hash.

Main features

• Guided reset: A single confirmation followed by preparation, WordPress reinstallation, and final cleanup, with visible status and progress.
• Verified WordPress files: Checks the official WordPress package and core-file integrity before using it.
• Administrator access retained: Keeps one selected administrator account and its password hash, subject to the eligibility checks shown before confirmation.
• Resumable recovery: Maintains a private operation journal; verifies the actual server state after interruptions rather than blindly repeating destructive requests.
• Safety-oriented preflight: Checks files, permissions, SQL structures, supported paths, locks, HTTPS and public access restrictions before destructive steps.
• Strict cleanup boundaries: Limits the reset to the target WordPress installation and temporary resources demonstrably owned by the current operation.
• Better troubleshooting: Gives clearer failure codes and a read-only progress display without exposing database contents or private recovery files.

What’s improved in version 0.1.2?

This update concentrates on interruptions, hosting compatibility, accurate progress and narrowly scoped cleanup. It improves the handling of HTTP 502/503/504 responses, stale browser state, interrupted SQL preparation, proxy-modified HTTP responses, cache-related rewrite rules, selected symbolic links, and the final cleanup of verified operation-owned resources. A new optional on-screen terminal view describes confirmed progress and shows the target WordPress version and downloaded package size; it does not run shell commands. See the detailed 0.1.2 changelog below.

Important: destructive operation. This is not a backup, migration, or site-recovery tool. A completed reset permanently removes the existing website and its content, including themes, plugins and media according to the approved cleanup scope. It cannot reconstruct your previous website after irreversible deletion. Create and independently verify a full filesystem and database backup before starting.

A temporary standalone recovery runner may continue the operation while the original WordPress core is unavailable. Its private operation journal is placed outside the public document root. The runner, locks, and associated resources are subject to ownership and state checks before cleanup. Remote sites require HTTPS. Plain HTTP is permitted only on strictly local development installations with explicit approval.

Compatibility: Intended for supported single-site installations with a conventional, writable WordPress layout, direct filesystem access, a compatible SQL database and a private recovery area. Multisite, FTP-only access, unverified shared resources and ambiguous server configurations are refused. Support for any particular hosting provider must be confirmed by testing its actual server configuration.

Security and limitations

Reset and recovery require administrator permissions, explicit confirmation, verified state and appropriate authenticated tokens. Before destructive work, the plugin checks the target site, SQL structure, public HTTP isolation, file ownership, WordPress package integrity and relevant filesystem protections. It rejects unsafe links and unidentified protected resources. Certain precisely identified terminal symbolic links within wp-content may be handled without following their external targets; symbolic links replacing protected core directories or traversing the core tree remain unsupported.

The recovery runner must operate independently while WordPress files are replaced, so this plugin performs some low-level filesystem and SQL operations that ordinary plugins do not. The temporary standalone PHP runner, private recovery journal and their cleanup safeguards should receive individual WordPress.org review. Static analysis success is not an approval or exemption by the WordPress.org review team.

Host-specific behavior can vary with web-server routing, PHP handlers, reverse proxies, object caches, must-use plugins, SQL privileges and filesystem permissions. Passing preflight does not guarantee an uninterrupted reset or restoration of the original website. Use on an expendable staging site before any production decision.