Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Publish process to select what will be included

Step 0 - make copy

If option “Use database copy” is selected, a copy of the database will be created. Option is available in version 5.2 and later.

Step 1 - collect information

Select all information which may be included in the publication.

Publication type

What is included

XML

All presentations which are marked with mode IncludeInPublish.

Remote, Site, Offline, Sync

All presentations which are referred from the selected catalogue. Referred information includes direct usage, replacements and references.

Also include all presentations which are marked with mode IncludeInPublish.

Select limitations of what is included based on specifications, see below.

...

Reset will only make a reset of the web viewer site pointed at in the publish. This setting cannot be combined with any of the previous, and is typically used when web viewer is connected directly to the Manager site database.

Validate will trigger validation to Accept validate errors Validation will run at publish. The vaildation will be run when the publication database is completely generated as a final step before uploading it to the web viewer. If publication fails, the publish process will be aborted. Validation need to be configured for this option to work properlyThis option will make validation errors to be accepted.

Prune empty nodes will remove empty nodes at publish, see step 5 above.

Rebuild indexes will make the publisher rebuild index of web viewer after completed publish. This normally is not needed but may improve web viewer performance.

Use database copy will make a database backup at start of publish process and then run publish process from the copy. This prevents data from changing during the process and can be useful if imports may run at the same time, but at the cost of some disk space and slightly longer publishing process. Option is available in version 5.2 and later.

Info

Publish same content to two web servers

If the exact same content is to be published to two different web servers, e.g. in two different regions, two publications will be needed. In order to avoid to run generate two times this setup can be used:

In the first publication: Check Generate and uncheck Erase after. Select a temporary site name.

In the second publication: Uncheck Generate and select the same temporary site name as in the first. Now the already generated site will be used.

 

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@1ecd09showSpacefalse
sortmodified
typeshowSpacepagefalse
reversetrue
labelstypePublish Permissionspage
cqllabel in ( "publish" , "permissions" ) and type = "page" and space = "ASKB"
labelsPublish Permissions


Page Properties
hiddentrue


Related issues