Workflows in TYPO3 Content Publisher

Content Publisher for TYPO3 - flexible and versatile

Daily requirements

The following requirements are desirable for the daily use of a content management system:

  • An editor makes several changes to the content of a page that are to be published at a specific time
  • One (or more) additional instances must be able to review editorial work before it is published
  • Ideally, the TYPO3 Live environment should not contain any Backend users, to make break-ins as difficult as possible

Publish content and files simply by clicking

Parts of these requirements can be realized with the help of workspaces in TYPO3 (working environments). However, many people shy away from this due to lack of compatibility with various extensions or performance.

We offer our customers a tool to easily map the requirements listed above: The Content Publisher for TYPO3 CMS can publish content and files with a simple click or after a complex defined workflow has been processed. The principle behind this is simple: A split on two separate servers offers a number of advantages.

Split between two servers

For example, the editors' working environment (stage server) can be located in a secure network, but the actual live environment (production server) can be publicly accessible.

Changes can be made without being immediately visible to every website visitor. Even major restructuring measures can be prepared, optimized, released and published at a specific time.

The advantages of the Content Publisher

Entwicklung

Intuitive operation

The modern designed user interface allows an intuitive operation without great training effort.
tanja_Support

Highest security

The transfer of assets and content is exclusively via secure connections (SSH/SFTP). This eliminates the need for backend users on the live system.
Check

Future-proof

The Content Publisher will support all upcoming TYPO3 versions.
Deployment

Complex Workflows

A workflow module enables predefined workflows with any number of definable steps. The workflow process starts automatically when a data record is changed. (Enterprise Edition)

Publish contents per click

External content

To use this content (Source: www.youtube-nocookie.com ), please click to Accept. We would like to point out that by accepting this iframes data to third parties transmitted or cookies could be stored.

You can find further information in our Privacy policy.

Architecture close to the TYPO3 standard

External content

To use this content (Source: www.youtube-nocookie.com ), please click to Accept. We would like to point out that by accepting this iframes data to third parties transmitted or cookies could be stored.

You can find further information in our Privacy policy.

Features

External content

To use this content (Source: www.youtube-nocookie.com ), please click to Accept. We would like to point out that by accepting this iframes data to third parties transmitted or cookies could be stored.

You can find further information in our Privacy policy.

Workflow Demo

External content

To use this content (Source: www.youtube-nocookie.com ), please click to Accept. We would like to point out that by accepting this iframes data to third parties transmitted or cookies could be stored.

You can find further information in our Privacy policy.

View into the backend of the Content Publisher modules

Simple operation

Editors can see changes between instances at a glance and transfer content from Stage to Live at the click of a mouse.

 

Large extension support

The Content Publisher supports almost all common TYPO3 extensions, as long as they have been created TYPO3-compliant (TCA).

 

Facts as PDF

Would you like a detailed description with all facts? You can download it here as PDF-Factsheet.

Content Publisher:

The editors can now publish promptly themselves ...

"... our support as admins is no longer required. Due to the selective publishing, it is no longer necessary for the whole instance to be in a publishable state at once. In addition, the integration of external editors has become much less complicated because the changes go through a proper release process.“

Sven Job
Editor featuresCommunity editionEnterprise edition
PublishPages, Files, ToolsPages, Files, Tools
Filter listssvgsvg
Compare Viewsvgsvg
Exclude tablessvgsvg
Configuration perPagetree, UserPagetree, User
Workflows per Page, Record
Team communication svg
Single User communication svg
Single Record Publishing svg
Scheduled Publishing svg
Accelerated BE view svg
Fire And Forget Publishing svg
Solr support svg

fal_securedownload support

 svg
Admin featuresCommunity editionEnterprise edition
Testssvgsvg
Relation breadcrumbsvgsvg
Logging in databasesvgsvg
Debug optionssvgsvg
Handle special characters (e.g. German Umlauts) in filenamessvgsvg
Clear FE cache on live serversvgsvg
Clear and update RealURL cachesvgsvg
Table operationsPublish, Import, BackupPublish, Import, Backup

Configuration Wizard

 svg

Pricelist for Enterprise Version

When publishing multiple languages, the workspaces are usually brought to their knees!

"Since we started using the Content Publisher, that's gone. The system is very robust and also the performance is better than with workspaces. We always had problems with self-developed extensions that were not optimized for workspaces. Now we can simply use identical code on both systems, which is a great relief.
We wanted the security of the protected backend right from the start. The Content Publisher gave us exactly that."

Hans Müller
Stefan Busemann

Projects and products in the TYPO3 area?

Do you have questions about TYPO3 projects and products?

Our managing director Stefan Busemann will be glad to help you.

Stefan Busemann |  Management & customer service