Instant Publishing

The instant publishing feature allows modifying the default publishing behavior of Gentics Content.Node. Typically, changes made to pages, templates and other objects will not be updated in their corresponding ContentRepositories until the next publish run is performed. When instant publishing is enabled, changes made in the CMS will be reflected in configured ContentRepositories immediately when a user marks the modified objects to be published.

1 Configuration

To enable instant publishing, add the following setting to the node.conf and restart the Tomcat server.

node.conf

$FEATURE["instant_cr_publishing"] = true;

Instant publishing must then be activating for each ContentRepository individually by enabling the “Instant Publishing” checkbox in the ContentRepository’s properties.

2 Use Cases

The primary intended use of instant publishing is in combination with Frontend Editing . Since by default, modified pages are not updated in ContentRepositories until a publish run is performed, frontend editors would not see their own changes immediately. By activating instant publishing, their changes will be reflected in the frontend every time they publish the page they are working on.

3 Limitations

When publishing multiple pages at a time, instant publishing will be ignored and the selected pages will not be published to the configured ContentRepositories until the next publish run is performed.

Instant publishing also has no effect on deleting collections of objects at once, so when multiple objects are deleted simultaneously, they will not be removed from ContentRepositories until the next publish run. Similarly, folders will also not be instantly removed from ContentRepositories when they are deleted.