capable_never_publish label
Add the capable_never_publish label to a page and it will never be published. It is a permanent, per-page opt-out. Any attempt to publish the page is recorded as Failed, with the reason "Publishing disabled by label".
#Where to find it
Add the label to any page you want to keep out of publishing.
#Where you do it
These are the places you manage publishing around the label.
Task | Where |
|---|---|
Turn on publishing for a space and choose where content goes | Space settings → Publishing → Setup tab (or the Settings section inside the Capable Publishing space page) |
Decide whether people can publish by hand, and whether they must leave a comment | Space settings → Publishing → Setup tab |
Choose where published pages land and whether the page tree is preserved | Space settings → Publishing → Structure tab |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Enable publishing | Space settings → Publishing → Setup tab | Allows content from this space to be published to another space. |
Target space | Space settings → Publishing → Setup tab | Chooses where approved content is published. |
Allow manual publishing | Space settings → Publishing → Setup tab | Lets users publish content manually from the page byline. |
#Worth knowing
"Save without rebuild" does not always prevent a rebuild. On a space that is already enabled, a rebuild starts whenever a saved change affects the hierarchy mode, parent page, homepage inclusion or target space, whichever button you press.
The Allowed publishers list takes individual users only. There is no group option, unlike Approval, which has both a user list and a group list.
The Publish button's space-administrator fallback checks whether you administer the target space, but publishing itself checks the source space. If you administer the source space but not the target space, the Publish button is hidden even though publishing would have been allowed.
You cannot save the configuration while a cleanup or rebuild is running for the space, and bulk publish is blocked at the same time. The check is best effort: if the app cannot work out whether a task is running, the save goes through.
There is no setting for "publish as user", but the behaviour is real: if the app itself cannot write to the target space, it falls back to a nominated account.
There is no unpublish or delete action. "Clear state" only breaks the link, changing the target space only clears records, and Reset to default leaves every published page in place. Delete published copies by hand in the target space.
#Related
How it actually behaves.
