Publishing folders
Publishing a folder also publishes what is inside it: once the folder exists in the target space the job walks its child pages and child folders (250 per query) and publishes each of them. In bulk runs folders are given a priority boost so they are created before the pages that go inside them.
#Where to find it
Publishing a folder from the byline or in a bulk run
#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
There is no server-side enforcement of which content types may be published. The byline gate is client-side only, the equivalent server check is disabled, and the server accepts pages, blog posts and folders regardless of the space setting.
The standalone Publishing app also comes with the Capable content indexing switched off entirely; its publish search fields exist only because they are written at publish time.
The publish record and all 13 of its search fields carry a prefix unique to each app, so a search or CQL query written for the standalone Publishing app will not match the Suite or the Approval app. Moving between apps loses all existing publish search data, and installing two Capable apps that ship Publishing produces two independent publish records on the same page.
Three shipping apps bundle Publishing: Publishing for Confluence, the Capable Suite, and Approval for Confluence. If more than one is installed, a page can carry two independent publish states and show two Publish buttons, and nothing in the product arbitrates between them.
If the app itself lacks write permission on the target space, publishing fails. The settings screen shows an error banner, but the configuration can still be saved.
#Related
How it actually behaves.
