WordPress Integration
Operate FileToWeb from WordPress, publish WordPress-local HTML, and control when visitors see HTML or the original PDF.
This guide applies to FileToWeb Integration 0.1.34 and later.
The FileToWeb WordPress integration converts PDF sources, tracks processing, stores a WordPress-local HTML copy when conversion is ready, and keeps the original PDF intact.
Choose the workflow you need
- Setup and connection: install the plugin, create an API key, and verify the workspace connection.
- Daily operations and migration: sync new PDFs, poll processing, migrate existing files, and understand every settings-page action.
- ProudCity Documents and Meetings: operate Proud Document previews and independent Agenda, Agenda Packet, and Minutes conversions.
- Convert PDF to a WordPress Page: intentionally create an editable draft WordPress Page.
- Public replacement and plugin lifecycle: choose whether visitors see HTML or PDFs and understand deactivation versus uninstall.
- Troubleshooting and support: resolve connection, credits, polling, processing, and preview issues.
Core guarantees
- The original WordPress PDF is not deleted or overwritten.
- Public replacement begins only after a complete WordPress-local HTML copy is ready.
- While processing, public links continue using the original PDF.
- Repeated sync requests are idempotent. An unchanged source does not start a duplicate conversion.
- Administrators retain links to the original PDF, generated HTML, FileToWeb Studio, and the WordPress-local copy.
- Customer-facing errors use a safe message and support reference rather than exposing internal processing details.
Quick decision table
| Desired outcome | Administrator action | Existing local HTML | Public result |
|---|---|---|---|
| Convert new PDFs and use ready HTML | Enable FileToWeb and Public replacement | Created and updated | Ready HTML replaces supported PDF previews and links |
| Pause future sync and polling | Deactivate the plugin or turn off Enabled | Preserved | Completed ProudCity previews can remain available |
| Return the site to PDFs | Turn off Public replacement and save | Preserved | Original PDF behavior returns |
| Resume ready HTML | Turn Public replacement back on | Reused | Ready local HTML returns |
| Remove FileToWeb data from WordPress | Uninstall the plugin | Removed | Original PDFs return |
Read Public replacement and plugin lifecycle before deactivating or uninstalling the integration.
WordPress and ProudCity scope
The plugin supports ordinary PDF Media attachments and literal PDF links while it is active. It also has guarded integrations for ProudCity Documents and Meeting materials.
ProudCity releases that implement the provider-neutral preview contract can continue serving completed Document and Meeting HTML previews after FileToWeb is deactivated. Generic links in arbitrary page or widget content still require the active plugin to rewrite them.
Permissions
Default permissions are deliberately conservative:
- Global settings and migration controls require the ability to activate plugins.
- Document and attachment sync actions require the ability to edit other users' posts.
- Pages > Convert PDF to Page requires the ability to publish Pages.
Site owners can alter these capabilities through WordPress filters when their editorial model requires different roles.