WordPress
How WordPress sync worksUnderstand how Workover pushes, pulls and syncs content with WordPress through the REST API, and what a project sync overwrites or protects.How to publish a document to WordPress for the first timeSend a Workover document to WordPress for the first time as a draft, pending, published or private post, schedule it, or link it to an existing post.How to push a document to WordPressPush edits from a linked Workover document to its WordPress post, see what a push sends, and handle a disabled Push button, conflicts and refusals.Pulling changes from WordPressPull the current WordPress version of a post into its linked Workover document, and see exactly what a pull replaces and what it leaves alone.Sync status and conflictsLook up each WordPress sync status in the WP tab and document list, what causes it, what clears it, and why a push can be stopped.Linking to other documents in a WordPress postLink one Workover document to another and see how links are rewritten to live WordPress URLs, or held, when you push, and what to do when one is held.Content types and collectionsChoose the WordPress content type a Workover document publishes as, see how the document list groups documents by type, and move a live post safely.Custom blocks, ACF and the block editorLearn how Workover handles custom blocks, ACF blocks and ACF fields in WordPress posts, and when to edit a post in the WordPress block editor view.Let Workover reach a site behind a firewall or Cloudflare AccessLet Workover reach a WordPress site behind a firewall, security plugin or Cloudflare Access by allowing its User-Agent or saving a service token.Application passwords are turned offTurn WordPress application passwords back on when a security plugin, host setting or missing HTTPS blocks them, then reconnect your site to Workover.Patchstack hardening settingsTurn off the Patchstack hardening settings that block WordPress application passwords or user enumeration so Workover can connect and list authors.