Order for the release

All outgoing references for the dependent release are only completely taken into account in one direction, in order to eliminate cyclical dependencies during the release.

Objects from page and media stores, which are referenced in the content, structure or content store, are taken into account during the dependent release. The reverse direction (site / media store→ page / site / content store ) does not function.

Objects from remote projects are not taken into account during dependent release.

If all dependent objects are contained in the release process, the following order has to be maintained:

• Release in the site store contains outgoing references to the content and the media store
• Release in the page store contains outgoing references to the media store

The following are not taken into account:

• Release in the page store contains no outgoing references to the site store.
• Release in the media store contains no outgoing references to the site store or the page store.

Other cases in which dependent objects are shown in the reference graph but are not released during the dependent release.

• Page → Page reference: Page with an FS_REFERENCE component, in which a page reference is referenced.
  → Only the page is released, not the dependent page reference.
• Page → Medium: Page with the page template in which a medium reference is hard-coded. For example: $CMS_REF(media:"XXX")$ in the HTML channel (see $CMS_REF(...)$).
  → Only the page is released, not the dependent medium.
• Page → Page reference / Medium: Page with CMS_INPUT_LINK-/CMS_INPUT_DOM-/CMS_INPUT_DOMTABLE component, in which a Medium and a Page reference is referenced.
  → The medium referenced (image) was also released, but the page reference referenced was not.
• Medium → Media file: In a CSS file (“file parsing”: yes), an additional hard-coded reference to a media file (for example, a picture) is made.
  → If the CSS file is released (“Specific release” -> “Release dependent objects”), the medium referenced is not released with it.

Under certain circumstances, there can be cyclical dependencies that cannot be released automatically and therefore have to be triggered manually. Example: There are 2 pages in the page store (Page 1 and “Page 2”), each with one section and a section reference to the other page's section: -- Page 1 ----- Section A ----- Section reference on section B of page 2 -- Page 2 ----- Section B ----- Section reference to section A of page 1 If the section references are not yet released, neither “page 1” nor “page 2” can be released automatically in this configuration. In order to release the pages, first one of the section references has to be deleted in order to display the cyclical dependency, for example, “Section reference on section B of page 2”. Then “page 2” can be released. Then the section reference has to be restored, after which “page 1” can also be released.

There are some cases in which the dependent objects are shown in reference graphs but are not released during the dependent release.