default label global value on app install is syncme
If Use sync-label is checked you can choose how it will be used.
When using sync-label you can either
Publish only content with the sync-label
Publish content without the sync label
You can choose to include child pages of a page with the sync-label.
The sync-label can also be set to be ignored for blog posts - all blog posts will then be published if blog posts are set to be published.
You can set Delete sync-label after publishing for all content in the source space after publishing. If set, the sync-label will be removed whether or not you have chosen to use the sync-label as a content filter.
Data to include
These options allow the choice of the content data to include in the pages and/or blog posts to be published.
Content labels (except the sync-label) can be included when publishing the content. If choosing to include content labels you can match the labels on the content in the source and published space.
If the Match labels option is checked
all existing published content will be updated to match labels on the content in the source space
existing source content labels will be removed
the sync-label, if present, will be added to the published content
The data can be set to include or exclude
source content page restrictions copied from the source content to the published content
"What did you change" user update comments
You can also choose to include data related to the ServiceRocket Scaffolding Forms and Templates app
Publishing Options
The published content can be set to have either
lastest modification date for the source content
the date of publishing
Comala Publishing is compatible with the Comala Document Management Family of Apps. Publishing the content can be set to the corresponding final (published) state in the Comalatech workflow applied to the source content.
You can also choose when publishing to
delete all content in the published space that is not in the source space
remove all page history form the published content
publish all the source congtent not just the content that has been updated
When you first publish a space you may need to set Publish to Delete Pages added in Target Space. This will cause the draft space home page to be published andto become the published space home page. The original home page in the published space is deleted.
If you don't want to publish the draft space home page you can configure the draft space Publish settings to ignore Top-level pages in the draft space for the publishing. This setting also means that any orphan pages in the draft space will not be published.
Display options
To help identify the source and published content a draft watermark can be added to the source space icon.
You can also choose to enable the addition of publishing status lozenges to your content to help in tracking the current status of your publish space and source space.
If DisplayPublishing Status Lozenge is checked the publishing status lozenge is displayed on the source space content.
The lozenge on each piece of content
is set as PublishedPUBLISHED when content is synchronized
is Out of SyncOUT OF SYNC when the content is not synchronized
is New NEW when the content has not yet been published
If you are using Comala Document Management which provides its own status lozenges, it is recommended that you disable the display of the Comala Publishing app lozenges in the source space.
If the Publish Settings are changed - for example, the option Always Publish is checked - this may cause pages to be displayed as out of sync in View Changes. Content will also be displayed in the published space with an Out of Sync lozenge.
Target space publishing lozenge
The behavior of the publishing status lozenge on the target space content is not affected by the DisplayPublishing Status Lozenge option.
The publishing status lozenge displayed on the target space content is dependent on the current user Confluence permissions on the content in the source space.
lozenges are displayed on the target space if the current userhas at least view permission on the source space content
lozenges are not displayed if the current userdoes not have viewpermission on the source content
The display of the target content link to the source space content is also dependent on the user permission on the source content
content and state published will be based on current Publishing Settings
Changes to Publish Page scope settings will be applied to Publish Space scope settings.
Publish Page scope can be enabled/disabled in Settings.
If disabled, this option lets you restrict space admins to whole-space publish.
If enabled then users can publish individual content even if it is not included in the Publish Options Content Filters for content to be published. For example, if blog posts are not checked in Content Filters they will not be included in any whole space publish but can still be published individually by a user from the page view.
CONTENT FILTERS
Copy Blog Posts
Blog posts are included in the publish. If not selected, blog posts are ignored.
Copy Pages
Pages are included in the publish. If not selected, pages are ignored.
Ignore Top-level Pages
Don't publish top-level pages (such as the space homepage) and other orphan pages. If the space has multiple page trees each starting with a top-level page, each top-level page will not be published.
If checked, the sync-label synchronization will be applied to the page with a sync-label ANDALL its child pages.
Ignore sync-label for Blog Posts
If selected, the sync-label as defined in Publishing Configuration in Confluence Admin is ignored for blog posts. All blog posts will be published (if set in the content filter) irrespective of the sync label.
Delete sync-label after publishing
If checked
the sync-label is removed from all content in the source space after publishing is complete
This will occur whether or not the sync-label is used.
For example, let's say the sync-label is private and you add the label private to a draft space page. If this option is selected then after the space is published, the private label is removed from the draft space page.
DATA TO INCLUDE
Labels
If selected, labels are published on target pages, blog posts, and attachments.
if a global sync-label has been set this will not be included
Match labels
Checking this option causes an exact copy of all labels from a draft page/blog post to be added to the published space page/blog post including any sync-label.
Any existing labels on the content in the published space are removed and replaced by the labels on the content in the draft space.
Content Properties
if checked Content Properties associated with other plugins will be published.
only the properties with prefixes specified in the global app configuration by Confluence administrator are published
Page properties are attributes associated with a page usually defined by other apps. See the other app's configuration to determine the prefix of these properties.
Restrictions
If checked
publish source page with any added page restrictions
page restrictions in published space will be replaced
Scaffolding
If active (ServiceRocket Scaffolding app or macros enabled) and checked
publish the scaffold data
Note that only the latest version data is published.
Version Comments
Publish the page's version comment (any change comment added by a page editor on updating the content).
PUBLISHING OPTIONS
Set content modification date in target space as:
Latest modification date
Checked by default
on publishing, the modification date will be taken from the item (page/blog post/attachment) in the source draft space that is being published
Publish date is unchecked
Publish date
If checked
for published pages, blog posts, and attachments the modification date will match the date the publishing occurred
Latest modification date is unchecked
Use final state
If checked
publish the version of the content corresponding to the Comala Document Management Family of apps workflow final state
content that do not have a final state will not be published
This option only publishes content with a new final/published version since the last time the space was published.
Note
only use if a Comalatech workflow is added and applied in the space
that if Publish Page scope is enabled (Enable Single Page Publish), individual pages can be published, bypassing the workflow
Delete target space content (pages and blog posts)
If selected, content that exists in the public space but not in the source (draft) space (out-of-sync pages) are deleted. If not selected, out-of-sync pages are unaffected. Pages that only exist in the public space are not deleted.
A notification on View Changes shows pages that are out of sync: pages exist in the public space but not in the draft space.
Override Content
If selected, no new versions are created. Page history is not kept
if the page doesn't exist in published space, it will create that page with version 1. Every time the page is published, that version will be replaced
if the page already exists with multiple versions in the published space, it will just replace the most recent version with new content
Always publish
If unchecked (default)
only the elements of content that have changed will be updated in the published space
If checked
all space pages and blog posts are published even if no changes have been made
ignores the manifest record (as seen on View Changes) that shows which pages and blog posts need publishing
Note that the View Changes report (the manifest record) may change if publishing options are changed.
DISPLAY OPTIONS
Draft Watermark
If checked, a draft watermark is displayed above the space logo when you are in the draft space.
Controls the display of the publishing status lozenge on content in the source space
If checked
a lozenge for the current status of publishing synchronization is added on pages and blog posts in the source space
Recommend that this be disabled when using Comala Document Management to handle publishing which provides its own status lozenges.
Note: the behavior of the lozenge display on the target content is not affected by this option setting. The display of the publishing status lozenge on the target space content is dependent on the user permissions for the source content.
Related Pages
Unable to render {children}. Page not found: Publishing dashboard - space tools.