Export and published sites
Start from what you are seeing rather than from what you think is broken. Each page below names the symptom, explains why it happens, and says what to do about it.
Several of these are the product working as designed, which is worth knowing before anybody raises a ticket.
#At a glance
Symptom | Usually because |
|---|---|
Am a space administrator of the source space, but the Publish button is still hidden and the space p | The byline's administrator fallback checks whether you administer the TARGET space, while the server checks whether you administer the SOURCE space. A source-space administrator who is not a |
Saved the Setup tab and manual publishing turned itself off, even though I never touched that switch | The settings screen seeds the manual-publishing switch to off before your first save, while the value actually stored for an untouched space is manual + automatic. Saving the form therefore |
Page approved by the right people never published, and shows Failed with "Parent page is not publish | With "Preserve hierarchy", only a manual publish will automatically publish the ancestors it needs. An approval-triggered publish never does. It can only reuse a parent that is already publi |
Nothing publishes when approvals are approved, and there is no "Publish approved pages" button | You are running the standalone Publishing app, which does not include the Approval capability at all, so nothing can ever queue an approval-triggered publish there. |
Page I published shows Failed and the reason is "Publishing disabled by label" | The page carries the capable_never_publish label, which permanently excludes it. |
Somebody deleted the published copy, but the source page still says Published | The delete-cleanup behaviour does not run. In the Suite it is switched off; the standalone Publishing app and the Approval app do not even subscribe to page-deleted events. |
Pressed "Save without rebuild" and my published pages moved anyway | The server starts a rebuild whenever the saved settings change the hierarchy mode, parent page, homepage inclusion or target space on an already-enabled space, regardless of which dialog but |
Restricted source page was published and now anyone in the target space can read it | Page restrictions are deliberately not copied. A restricted source page becomes an unrestricted page in the target space. |
Publishing a page produced a second copy instead of updating the existing one | The stored link between the source page and its copy was lost. |
Published page links to another page, but the link opens the original in the source space instead of | The linked page had not been published at the time. Links to unpublished pages are left pointing at the source, and the app records them as "missing links". |
Nobody was told that a publish failed | Publishing sends no notifications of any kind. No email, no Slack, nothing. |
Pages stopped going Outdated / Moved / Out of sync, but manual publishing still works | All the Confluence event listeners that keep statuses current only run on a licensed site. On an unlicensed, expired or evaluation-without-licence site they do not fire. |
Published blog post never goes Outdated even after I edit it | Publishing only listens for edits to pages. Nothing listens for blog-post edits, so a published blog post can never be marked out of date. |
All publishing jobs fail, or the space page shows nothing at all and never finishes | The app's background processing store is missing or damaged. |
#In this section
#Related
Most of these are expected behaviour.
