Skip to main content
FileToWeb
Sign Up

Public Replacement and Plugin Lifecycle

Control whether visitors see WordPress-local HTML or original PDFs and understand disable, deactivate, and uninstall behavior.

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

Return one item to its PDF

In FileToWeb Integration 0.1.41 or newer, editors can withdraw one HTML preview while leaving public replacement enabled for the rest of the site:

  1. Open the Proud Document or PDF attachment, or open the Meeting that contains the material.
  2. In its FileToWeb panel, click Show original PDF publicly.
  3. Verify the public page in a signed-out browser.
  4. Continue editing, syncing, or checking progress as needed. The updated HTML stays private while the PDF remains public.
  5. When the HTML is ready, click Restore HTML preview.

Restore is intentionally manual. WordPress first verifies that the local HTML copy is ready and matches the current PDF. If the PDF changed or the local preview is incomplete, the PDF remains public and the editor must sync or refresh before trying Restore again.

The preference belongs to the source PDF. If the same Media attachment is reused by multiple Documents or Meetings, Show original PDF publicly affects every place that attachment appears. Pausing one Meeting material does not affect the Meeting's other PDF attachments.

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

FileToWeb Integration plugin row with the Deactivate action

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.

Site-wide and per-item precedence

The site-wide Public replacement setting takes precedence. If it is off, every source uses its original PDF regardless of individual item state. When it is on, an item marked Public view: Original PDF remains on its PDF until an editor restores that item's HTML preview.

Do not delete local preview artifacts to accomplish a temporary fallback. The per-item control preserves the current bundle and allows later syncs to refresh it privately.

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.