About this plugin
Discovers published public content types, taxonomy archives and linked pagination. Fetches anonymous rendered responses, collects common HTML and CSS dependencies, rewrites local URLs and packages the result. On a local WordPress site, a supported browser can instead save the exact generated file structure into a folder selected by the administrator, without creating a ZIP.
Register each form manually: name, public page URL and unique form ID or CSS selector. Verify the match and fields, then choose Formspree and save its endpoint URL. Only registered forms are changed.
Legacy automatic inventory rules are not imported; register intended contact forms again. Settings are frozen when each export starts; changes require a new export.
Requirements and scope
PHP DOM (form verification), MySQL/MariaDB named locks, writable private system temporary directory outside WordPress, and anonymous HTTP access to the site’s own public URLs are required. ZIP exports also require PHP ZipArchive. Local-folder export is deliberately available only when WordPress itself runs locally; it requires a Chromium-based browser with the File System Access API from localhost, HTTPS, or another trusted local address.
It is unavailable for sites running on a hosted server. Self-signed certificates, HTTP authentication and blocked loopback requests need server configuration; this release does not bypass them.
Up to 10,000 URLs, 32 MB per source response, one job per site. The last successful export remains available during a new attempt. It is deleted only after the replacement ZIP passes verification.
Abandoned unfinished attempts expire after 24 hours without progress; hourly WP-Cron cleanup requires site traffic. A manual Delete export files button removes the generated files and cancels the current attempt. Failed filesystem deletions are reported and retried; only registered plugin-owned temporary directories are visited.
Download promptly: system temporary-file cleanup can expire an export. Export records remain after plugin removal; this release has no uninstall data deletion routine.
This is a public rendered snapshot, not a PHP or database backup. Media must be discovered through supported page/CSS references; the entire media library is not copied. Unlinked runtime assets, JavaScript-created forms, computed JavaScript URLs, external assets, query-string content variants, AJAX filtering, search, booking availability, carts, logins and payments require separate integrations.
Choosing types controls individually discovered records; archive/homepage output remains the HTML served by WordPress and can mention other content types.
Formspree delivery supports ordinary named text/email/telephone/number/date fields, textareas, selects and choices. io/f/ endpoint per registered form, plus an optional subject. Hidden fields and WordPress internal actions are excluded except supported CAPTCHA response tokens; password/file forms are blocked.
Multi-step forms, dynamic widgets, arbitrary JSON endpoints and FormSubmit are not supported in this release. The browser navigates to Formspree for its verification and result; this is not an AJAX success-message integration. JavaScript is required.
Standard submit/click events are intercepted. Custom JavaScript that directly sends requests requires an adapter and review. WordPress REST discovery markup may generate conservative dynamic-dependency warnings.
Warnings are capped at 300 entries. There is no guaranteed offline completeness for arbitrary themes and plugins.
Bricks Builder and JetEngine are not certified by this release. Server-rendered public output is the target; test a representative site before deployment. A ZIP can be structurally valid while still containing interactions that need a backend.
Translations
English source strings and POT are included. Arabic PO/MO are supplied separately. mo in wp-content/languages/plugins/ or import the PO through your translation workflow.
The administrator locale controls the interface; the site locale controls exported form notices.
Privacy
No analytics. Form delivery is disabled by default. io/.
No form data is sent by verification, saving settings or generating a ZIP. The public Formspree endpoint is embedded in the exported HTML; recipient settings and secret keys belong in the Formspree dashboard. Providers are independent and we do not guarantee their prices, limits, privacy policies or continued availability.
io/ before enabling it. Export HTTP requests go to the source site and referenced font/CSS providers. Referenced font files and external CSS (including Google Fonts CSS endpoints) are downloaded into the ZIP and rewritten to local paths.
External requests use WordPress safe HTTP validation with TLS verification, no cookies, and validated redirects. Other external assets remain external and are reported. Unavailable fonts cause an incomplete export.
The optional support link opens PayPal only when clicked. The report contains source URLs and form IDs and is downloaded separately from the public site ZIP.
SFTP publishing
SFTP is optional and sends exported public site files to the server you configure. The plugin does not provide hosting or transmit credentials to a separate vendor. Enter the host, port, username, existing absolute website directory and SHA256 host-key fingerprint from your host.
Password and SSH private key authentication are supported. Credentials are encrypted with this installation’s WordPress security keys; changing those keys requires re-entering credentials. OpenSSL is required for credential storage; the PHP SSH2 extension is not required.
The server must allow outgoing connections from WordPress and support the OpenSSH posix-rename extension for atomic per-file replacement. A dedicated remote folder without symbolic links is required. Files up to 128 MB are supported.
com/travel/. The server directory is separate from this public hosting path.
A full local build is verified before deployment. Changed files are uploaded in 1 MB batches. Unchanged files are content-verified against the server but not uploaded again.
This verification downloads remote file contents, so it still uses bandwidth. Keep the export screen open; pause/resume and retry preserve progress. Visitors may see a mixture of old and new pages while publishing: replacement is atomic per file, not for the entire website.
Obsolete tracked files are removed after uploads complete. Untracked files, symbolic links and externally changed files cause a conflict instead of being overwritten or deleted. The remote folder is not automatically adopted if it already contains website files.
One destination is supported; after publishing starts its host, port, username and directory are fixed to preserve ownership history. Credentials and the verified host fingerprint can be updated. One small remote ownership marker and a private local path/hash ledger are retained.
Do not delete the marker or the local ownership option. A lost ledger is not rebuilt by guessing ownership.
No full remote backups or version folders are created. One temporary upload file can remain after a connection failure; the next successful deployment reuses/removes it. A cancelled deployment may have already updated some live files; the next complete deployment reconciles all tracked files.
Deleting local export files does not delete the live site or its ownership history. Completed SFTP builds are removed locally, and unfinished builds follow the existing expiry policy. The local export process and SFTP credentials are not included in the public website.
3, MIT licensed and namespaced to avoid conflicts. Original licenses and provenance are included in vendor/sftp.