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.
Comparison: Content Publisher vs. Workspaces
"In the Open Source environment and the usual alternatives Drupal, Craft, Umbraco, Joomla and also the newcomers such as Graf, Netlify, October or CMS Made Simple, TYPO3 with the Content Publisher Module alone is on a wide corridor. Even more so when the widespread PHP platform comes into question, TYPO3 remains the only Open Source solution with Enterprise capabilities," writes Daniel von dpool in his own blog post on publishing and workflows.
Early Access Program for TYPO3 12
All details about the development status of this extension for TYPO3 12 can be found on our EAP page.
The advantages of the Content Publisher
Intuitive operation
Highest security
Future-proof
Complex Workflows
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
Large extension support
The Content Publisher supports almost all common TYPO3 extensions, as long as they have been created TYPO3-compliant (TCA).
Simple operation
Editors can see changes between instances at a glance and transfer content from Stage to Live at the click of a mouse.
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.“
| Editor Features | Community Edition | Enterprise Edition |
|---|---|---|
| Publish records | Pages, Files | Pages, Files |
| Scheduled publishing |  | |
| Tools menu to analyze setup | | |
| Comparison view stage/production | | |
| Publishing of redirects | | |
| Exclude tables from publishing | | |
Publishing of single records | | |
| Button for publishing of all records | | |
| Workflow colors in page tree | | |
| Configuration options per | Page tree, User | Page tree, User |
| Workflows for | Page, Record | |
| Publishing notifications per group | | |
| Publishing notifications per user | | |
| Support of EXT:solr | | |
Support of EXT:solr fal_securedownload | |
| Admin Features | Community Edition | Enterprise Edition |
|---|---|---|
| Tools menu with tests for setup | | |
| Cross-Storage publishing | | |
| Breadcrumb to visualize relations | | |
| Logging of CP Operations | | |
| Debug-Options | | |
| Support of special characters (e.g. Umlauts) in file names | | |
| Clear caches on live system | | |
| Commands for table-operations | Publish, Import, Backup | Publish, Import, Backup |
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."
125.549
downloads
98.817 downloads over packagist.org / 26.732 downloads over TYPO3 extension repository
Every year again: Early Access Program 2024
Content Publisher 11 for TYPO3 V11
in2publish Version 10.2: SimpleOverviewAndAjax + SimplePublishing = SimplifiedOverviewAndPublishing
in2publish Version 10.1 release
in2publish Version 10: Full speed ahead for TYPO3 v10
Content Publisher Enterprise Edition Release 9.4
Version history
Latest versions
| Version | Comment | Date | Link |
|---|---|---|---|
| 12.5.5 | Release Notes: https://github.com/in2code-de/in2publish_core/releases/tag/12.5.5 | 2024-10-09 | https://packagist.org/packages/in2code/in2publish_core#12.5.5 |
| 12.5.4 | Release Notes: https://github.com/in2code-de/in2publish_core/releases/tag/12.5.4 | 2024-09-25 | https://packagist.org/packages/in2code/in2publish_core#12.5.4 |
| 12.5.3 | Release Notes: https://github.com/in2code-de/in2publish_core/releases/tag/12.5.3 | 2024-08-26 | https://packagist.org/packages/in2code/in2publish_core#12.5.3 |
| 12.5.2 | Release Notes: https://github.com/in2code-de/in2publish_core/releases/tag/12.5.2 | 2024-05-28 | https://packagist.org/packages/in2code/in2publish_core#12.5.2 |
| 12.5.1 | Release Notes: https://github.com/in2code-de/in2publish_core/releases/tag/12.5.1 | 2024-05-14 | https://packagist.org/packages/in2code/in2publish_core#12.5.1 |
| 12.5.0 | Release notes: https://github.com/in2code-de/in2publish_core/releases/tag/12.5.0 | 2024-05-02 | https://packagist.org/packages/in2code/in2publish_core#12.5.0 |
PHP Package: in2code/in2publish_core, TYPO3 extension key: in2publish_core,
Number of releases: 115, Latest update: 2024-10-09,
Content publishing extension to connect stage and production server
