capable_never_publish label
A permanent per-page opt-out. Any publish attempt on a page carrying this label is recorded as Failed with the reason "Publishing disabled by label".
#Where to find it
Add the label to any page
#Where you do it
Task | Where |
|---|---|
Turn on publishing for a space and choose where conten | Space settings → Publishing → Setup tab (or the Settings section inside the Capable Publishing space page) |
Decide whether people can publish by hand, and whether | Space settings → Publishing → Setup tab |
Choose where published pages land and whether the tree | Space settings → Publishing → Structure tab |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Enable publishing | Space settings → Publishing → Setup tab | - |
Target space | Space settings → Publishing → Setup tab | - |
Allow manual publishing | Space settings → Publishing → Setup tab | - |
#Worth knowing
"Save without rebuild" does not prevent a rebuild. The server starts one whenever the saved configuration changes the hierarchy mode, parent page, homepage inclusion or target space on an already-enabled space, regardless of which button was pressed.
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 byline's space-administrator fallback for the publish restriction checks administration of the TARGET space, while the server checks the SOURCE space. A source-space administrator who does not administer the target space sees the Publish button hidden even though the server would have allowed the call.
Configuration cannot be saved while a cleanup or rebuild is running for the space, and bulk publish is blocked at the same time. But the block is best-effort: if the background tables cannot be read, the save is allowed through.
There is no control anywhere for "publish as user", yet the value is real: if the app itself cannot write to the target space, it falls back to that 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. Published copies must be deleted by hand in the target space, and nothing in the product says so.
#Related
How it actually behaves.
