How to push a document to WordPress

Once a document is linked to a WordPress post, editing it in Workover doesn’t change anything on your site until you push. This article covers pushing an already-linked document’s edits live, what a push actually updates on the post, and what to do when Workover tells you the WordPress copy has moved ahead of you.

Push your edits

1. Open the document and open the WP tab in the editor’s side panel.

   

2. Check the sync status pill at the top of the panel. If it reads “Unpushed changes” or shows a count of unpushed field edits, your edits haven’t reached WordPress yet.

   

3. Click Push.

   

If any suggestions in the document are still pending (not accepted or rejected), the Push button is disabled until you resolve them. Pushing sends the editor’s markup exactly as it stands, so an unresolved suggestion would put its tracked-change markers on the live page.

What a push changes on the post

A push writes to the linked WordPress post in one request. It updates:

• The post body, converted from the document into the post’s block markup (or sent as-is if you authored the body directly in the WordPress block editor surface).
• The title, if it has changed.
• Any field you’ve edited in the WP tab since the last push or pull: status, permalink (slug), excerpt, publish date, categories, tags, any other taxonomy terms, menu order, featured image, author, custom fields (ACF and registered post meta), and SEO fields for Yoast or Rank Math.

Images in the document that are still hosted by Workover get uploaded into the site’s own media library as part of the push, and the body is rewritten to reference them there, so the published post doesn’t depend on an image staying reachable from Workover.

After a successful push, the status pill returns to “Up to date with WordPress” and the other fields in the panel reflect what’s now live on the post. Everyone else on the project gets notified that the post was updated.

When Workover says WordPress is newer

Before writing anything, Workover checks whether the post has been changed directly in WordPress since your last push or pull. If it has, pushing is refused and you’re shown a dialog explaining that the post was changed in WordPress and that pushing would overwrite those changes. You’ll see the same warning if the push would drop content that exists on the live post but that the editor can’t represent (for example, an embedded video the document doesn’t have).

You have two ways forward:

• Pull latest from WordPress first. This replaces the document’s body and fields here with what’s currently live on the post, discarding anything you had staged but not yet pushed. Do this when the change made directly in WordPress is real content you don’t want to lose, then reapply your edits and push again.

  

• Overwrite anyway. This forces the push through, discarding the change that was made directly on the post. Use this when the difference doesn’t matter, for example when only WordPress’s own “last modified” timestamp moved, or when a plugin touched the post without changing anything you care about.

If the warning is about content the editor can’t represent rather than a change on WordPress (for instance, an embed), there’s no pull option, only the choice to overwrite or cancel and go edit the post directly in WordPress if you need to keep that content.

The status pill in the WP tab tells you which way things are out of sync before you even click Push: it distinguishes edits you haven’t sent yet from changes WordPress has that you haven’t seen.