EP Promote
EP Promote turns a PageMotor staging site into an approval desk. Every page you change on staging waits in a queue. When an approver clicks Approve, that one item is published to your live site, or to the ElmsPark edge, and a copy of what was there before is kept so you can roll it back.
Published by ElmsPark Studio.
Overview
Section titled “Overview”You install EP Promote on the staging site only. The live site needs nothing extra.
The plugin compares each item on staging with what it last published, so the queue shows only what is new or changed. Nothing reaches the live site until someone approves it.
Every approval and every rollback is written to a log, with who did it and when. After each publish, the plugin reads the page back from the destination to check it arrived.
Requirements
Section titled “Requirements”- PageMotor 0.11.5 or later on the staging site
- A staging site and a live site you control, or an ElmsPark edge account
Installation
Section titled “Installation”ep-promote.zipcomes with an EP Suite licence. ElmsPark supplies it directly (see EP Suite plugins); after install it updates through your site’s Updates screen.- On your staging site, upload it via Plugins → Manage Plugins. Activate.
- Open the plugin’s settings and choose where approved items go (see below).
- Add your destination’s address to Allowed hosts. Until you do, nothing is published.
Choosing where approved items go
Section titled “Choosing where approved items go”The setting Publish approved items to has two choices.
A live PageMotor site
Section titled “A live PageMotor site”Fill in:
- Live site address, for example
https://www.example.com. - Live site API token. Make a producer token on the live site under Admin → Manage API Access and paste it here. A producer token can read and write content and host images. It cannot install plugins or manage users.
This destination takes pages, HTML documents, the HTML Home, modular blocks and the 404 page.
Before publishing, the plugin checks that every plugin the page uses is active on the live site, and stops if one is missing. Images on the page are copied to the live site as well.
The ElmsPark edge
Section titled “The ElmsPark edge”The edge serves pages from Cloudflare, close to every visitor, without a PageMotor site behind them. Fill in:
- Edge address, the host name the pages are served on.
- Edge brand, the name the edge files these pages under (lower case letters, numbers and hyphens).
- Edge fallback, an
https://address visitors are sent to whenever the page cannot be shown. - Cloudflare account ID and Edge KV namespace ID, which ElmsPark gives you.
- Cloudflare API token, with Workers KV Storage: Edit on that account. It is only ever sent to Cloudflare.
The edge takes HTML documents and the HTML Home only. Each approval goes up as a new version with its images inside it, and the address switches to it only once every file is there. A page saved as a draft on staging goes up held, so it stays private until it is live on staging too.
A page is refused before anything is sent if it:
- uses a shortcode, because the edge cannot run plugins;
- uses a protected upload;
- has no buy link marked with
data-bridge, or is very short. The edge takes such a page down within a minute, so the plugin will not send it.
Allowed hosts
Section titled “Allowed hosts”Your API token is only ever sent to a host on this list. Only an administrator can change it, and it is kept apart from the plugin settings, which a producer can change.
Enter exact host names, separated by commas or spaces, for example www.example.com, go.example.com. A host must match exactly: a sub-domain of a listed host is not allowed.
The list is on the plugin’s settings page, between the queue and the history of recent publishes.
Who can approve
Section titled “Who can approve”The Approvers setting lists the people allowed to approve, by username or email, separated by commas.
- Left empty, only administrators can approve.
- With names in it, those people can approve, whether they are administrators, producers or signed-in users. A non-administrator approves from the bar on the page itself.
Rolling back is always for administrators only.
Approving a change
Section titled “Approving a change”There are two places to approve from:
- The queue, at the bottom of the plugin’s settings page, lists everything waiting, with an Approve button for each item.
- The bar on the page. When an approver views a changed page on staging, a small bar offers Approve and publish for that page.
When the destination changed since your last publish
Section titled “When the destination changed since your last publish”If someone edited the page directly on the live site (or on the edge) after it was last published from staging, approving stops and says so. That protects their edit from being overwritten without anyone noticing.
You can still publish over it. Confirm the second prompt, and the copy that was there is kept for rollback as usual.
Review links
Section titled “Review links”A review link lets someone without an account, such as a client’s marketer, approve one page.
- In the queue, click Make a review link next to the page.
- Enter who it is for. That name appears in the log.
- Copy the link that appears and send it to them. It is shown once and never stored, so it cannot be shown again.
When they open it, they see the page with the Approve bar. They can approve exactly the version they looked at, and nothing else.
- A link expires after seven days by default, and after 30 days at most.
- You can withdraw it at any time.
- It can never publish over a change made on the live site. That needs an approver.
Review links set no cookie and store no IP address or browser details. Pages opened with one send no referrer and ask search engines not to index them.
Rolling back
Section titled “Rolling back”Each approval in the history has a Roll back button.
- If the approval replaced something, the previous copy is put back.
- If the approval created the page, it is removed again.
- If it was the first approval of an HTML Home, the live site’s Home is switched back to how it was.
On the edge, rolling back is instant: it points the address back at the previous version, or takes the address down if the approval created it.
Rollback stops if the page was changed on the destination after that approval, if a newer approval is still in place, or if it was already rolled back.
For agents
Section titled “For agents”EP Promote registers these actions under EP_Promote for admin agents over the PageMotor API and MCP:
| Action | What it does |
|---|---|
queue | Lists staging content that is new or changed since its last promotion. |
approve | Publishes one item, keeping a copy for rollback. force publishes over a destination that changed. |
rollback | Undoes one promotion from the history. force rolls back even though the destination changed. |
history | Recent promotions and rollbacks, newest first. |
link | Records that a staging item matches a live item copied over some other way (live PageMotor destination only). |
hosts | Reads or replaces the allowed hosts list. |
share | Makes a review link for one item. |
shares | Lists review links. The links themselves cannot be shown again. |
unshare | Withdraws a review link at once. |
Troubleshooting
Section titled “Troubleshooting””Nothing is published after updating”
Section titled “”Nothing is published after updating””Add your live site’s host name, or your edge address, to Allowed hosts. Earlier versions trusted any address on the staging site’s own domain. This version sends a token only to hosts on the list.
”Approve says the page changed on the destination”
Section titled “”Approve says the page changed on the destination””Someone edited it there after your last publish. Check the live page first. If staging should win, confirm the second prompt to publish over it.
”The edge refuses my page”
Section titled “”The edge refuses my page””Read the message: the page uses a shortcode or a protected upload, or it has no data-bridge buy link. Fix it on staging, then approve again.
Feedback and corrections
Section titled “Feedback and corrections”For a question, a bug report or a feature request, open a ticket at help.elmspark.com. A real person, helped by AI, writes the reply. Usually within a few hours.
Changelog
Section titled “Changelog”- Changing this plugin’s settings over the API now needs an admin token. Producer tokens and AI apps connected through a producer account can still read the settings. Saving from the Admin screen works exactly as before.
- Now on the ElmsPark update channel. This is the first release you can install and update from your site’s Updates screen.
- Publish to the edge. A new setting, “Publish approved items to”, can now send an approved HTML document or HTML Home to the ElmsPark edge instead of a live PageMotor site. Each approval goes up as a new version with its images inside it, and the address switches to it only once every file is there. A draft on staging goes up held, so it stays private until it is live on staging too.
- The edge gets the same safety checks. A page that uses a shortcode, a protected upload, or no buy link (which the edge would take down within a minute) is refused before anything is sent.
- Rolling back on the edge is instant. It puts the previous version back at the address, or takes the address down if the approval created it. No file is ever rewritten.
- Approvers do not have to be administrators. Name someone on the Approvers list and they can approve from the bar on the page, whether they are an administrator, a producer or a signed-in user. With the list empty, only administrators can approve, as before. Rolling back stays with administrators.
- Review links. An administrator can make a link for one page with “Make a review link” and send it to someone without an account, such as a brand’s marketer. Opening it shows the Approve bar on that page only. It approves exactly the version they looked at, it expires (7 days by default, 30 at most), it can be withdrawn at any time, and the log shows who it was for. The link is shown once and never stored.
- Allowed hosts. Publishing now goes only to sites an administrator has put on the new allowed hosts list. After updating, add your live site (or edge address) to the list once, or nothing will be published.
- No more silent overwrites. If someone changed the page on the live site (or the edge) after it was last published from staging, approving now stops and says so. You can still publish over it after a second confirmation, and the copy is kept for rollback. A review link can never overrule this.
- Safer rollback. Rollback now stops if the live page was changed after that approval, if a newer approval is still in place, or if it was already rolled back.
- The live Home comes back too. Rolling back the first approval of an HTML Home now switches the live site’s Home back to how it was. A dormant HTML Home on the live site is kept and restored instead of being moved to the trash.