What "Publish again" does
No connector updates a post that is already published. What publishing a second time does on each destination, before you click.
Updated
In short. Publish again sends the article a second time. It never replaces a live post in place. On WordPress it creates a duplicate. On the Peach-hosted blog it moves the article to a new address and the old address stops working. The confirmation tells you the effect before anything is sent.
Why the button does not say "Update"
After an article has been published once, its button reads Publish again, not "Update" or "Re-publish". Those words would promise that your live post gets replaced where it is. No connector does that.
What happens on each destination
| Destination | A second publish |
|---|---|
| Peach-hosted blog | The article gets a new address. The old address stops working, so links to it break. |
| WordPress.org | Creates a second post. The first post stays as it was. |
The confirmation shown before a second publish states the effect for the destination you chose.
If you edited an article after publishing it
On the Peach-hosted blog
You do not need to publish again. The hosted page is served from the article as it is saved in Peach, so saved edits show on the live page at the same address.
Publishing again would only change the address and break the old one. Avoid it unless you want a new address.
On WordPress
Your edits are saved in Peach. They are not on your WordPress site. You have three choices.
Edit the post in WordPress. Open the post there and paste in your changes. This keeps one post and one address.
Publish again, then delete the first post in WordPress. Links to the first post's address will break unless you redirect them.
Leave it. If the change was small, the live post may be fine as it is.
Coming soon. Updating a published WordPress post in place. No connector does this today.
Before you publish the first time
- Check the article's quality result and read it through.
- Check the title. On the Peach-hosted blog the address is built from it.
- Check the call to action link works.
- Then publish.