Public Replacement and Plugin Lifecycle

FileToWeb separates conversion data from the decision to use converted HTML publicly.

Return the site to PDFs

To stop using converted files publicly while retaining them for a possible return:

1. Keep or reactivate FileToWeb Integration.
2. Open Settings > FileToWeb.
3. Clear Replace front-end PDF links with WordPress-local HTML when ready.
4. Click Save FileToWeb settings.
5. Clear any page cache and verify a public Document and Meeting page.

This disables the FileToWeb public preview provider and restores original PDF behavior. Existing local HTML artifacts and conversion metadata remain stored.

To resume, select Public replacement again and save.

If the plugin is already deactivated

The FileToWeb settings screen is unavailable while the plugin is deactivated.

If completed ProudCity HTML previews are still visible and you want PDFs instead:

1. Reactivate FileToWeb Integration.
2. Turn off Public replacement.
3. Save the settings.
4. Optionally deactivate the plugin again.

No valid API key or new conversion is required to change this local public-rendering preference.

Master Enabled switch

Turning off Enabled pauses plugin-managed sync, polling, and active-plugin replacement behavior. It is not the recommended control for returning durable ProudCity previews to PDFs.

Use Public replacement for the explicit HTML-versus-PDF decision.

Deactivation

Deactivation:

• Stops future FileToWeb sync and polling.
• Stops generic active-plugin link rewriting.
• Preserves API settings, document metadata, preview records, and local artifacts.
• Preserves completed Proud Document and Meeting previews on compatible ProudCity releases.

Deactivation is appropriate for pausing operational activity without destroying completed work.

Clearing or revoking the API key

Clearing the saved key in WordPress or revoking it in FileToWeb prevents future authenticated API operations.

It does not by itself remove local preview artifacts or tell ProudCity to return to PDFs. Turn off Public replacement if the public site should stop using ready HTML.

Uninstall

Uninstall is destructive for FileToWeb-owned WordPress data:

• FileToWeb settings are removed.
• FileToWeb preview records and metadata are removed.
• Local FileToWeb artifacts are removed.
• Supported remote WordPress storage cleanup is requested when configured.
• Public behavior falls back to original PDFs.

Use uninstall only when the customer intends to remove the integration rather than pause it.

Current per-document limitation

In version 0.1.34, Public replacement is a site-wide setting. There is no first-class Use original PDF for this document only control.

If one document must be excluded while other ready HTML remains public, contact the site operator or FileToWeb support before changing metadata manually. Do not delete local artifacts directly.

Verification checklist

After changing public behavior:

1. Open one Proud Document.
2. Open one Meeting with an Agenda or Minutes PDF.
3. Confirm Download still opens the original PDF.
4. Confirm the preview matches the selected HTML or PDF behavior.
5. Test in a signed-out browser.
6. Purge WordPress, reverse-proxy, and CDN caches if the old result remains.