When using a Content Management System the following requirements are desired frequently:
Parts of these requirements can be resolved by using Workspaces in TYPO3. However, many developers are reluctant to do so because of the lack of compatibilty with various extensions and performance issues.
We offer a tool to solve these requirements easily: The Content Publisher for TYPO3 CMS is able to publish content and files at a klick or after performing a complex predefined workflow. The architecture for this is very simple: Splitting the system into two separate servers provides a number of benefits.
By splitting the system into two servers the interface for the editors (stage server) can be located inside a protected network. The actual live server on the other hand is publicly accessible.
This allows that changes can be made without being visible on the website instantly. Even larger content reorganisation can be prepared, optimised, approved and published at a specified time.
When Publishing Multiple Languages Workspaces usually gave up!
"Since we use the Content Publisher that's not an issue anymore. The system is very robust and performance is better than with Workspaces as well. We always had problems with custom-built extensions that were not optimised for Workspaces. Now we can simply use identical code on both systems. Thats a great relief!
We wanted to have the security of a protected backend for a long time. The Content Publisher provides exactly that."
Editors can spot the differences between the servers at a glance. They can transfer content from Stage to Live with just a click.
The Content Publisher supports almost all TYPO3 extensions as long as they have been created in line with the TYPO3 standard (TCA).
You would like to have a detailed description with all facts? Download the PDF Factsheet (Enterprise Edition) here.
Content Publisher: TYPO3
Editors can now publish themselves without waiting...
"... because our support as admins is not required anymore. With selective publishing it is not necessary to have the whole server in a publishable stage at a specific time. Furthermore involving external editors has become a lot less complicated because the changes go through a proper approval process.“
|Editor features||Community edition||Enterprise edition|
|Publish||Pages, Files, Tools||Pages, Files, Tools|
|Configuration per||Pagetree, User||Pagetree, User|
|Workflows per||Page, Record|
|Single User communication||✓|
|Single Record Publishing||✓|
|Accelerated BE view||✓|
|Fire And Forget Publishing||✓|
|Admin features||Community edition||Enterprise edition|
|Logging in database||✓||✓|
|Handle special characters (e.g. German Umlauts) in filenames||✓||✓|
|Clear FE cache on live server||✓||✓|
|Clear and update RealURL cache||✓||✓|
|Table operations||Publish, Import, Backup||Publish, Import, Backup|
You have questions about this or other TYPO3 projects?
Stefan Busemann is happy to help you.