Content publishing extension to connect stage and production server

Installs: 38 203

Dependents: 0

Suggesters: 0

Security: 0

Stars: 39

Watchers: 13

Forks: 19

Open Issues: 2


9.5.0 2021-07-22 13:26 UTC


Latest Stable Version Build Status Latest Unstable Version License Codacy Badge


Content Publishing in TYPO3 - the easy way:

  • Intuitive Use
  • High Security
  • Future proof
  • Supports all extensions (with correct TCA)



This TYPO3 Extension is free to use. We as in2code and our developers highly appreciate your feedback and work hard to improve our extensions. To do so, in2code provides two extra days per month for coding and developing (Coding Night and Freaky Friday). During these days our more than 20 developers spend their time with improvements and updates for this and other extensions.

You can support our work here.

Thank you very much in advance.

Your in2code Team


The Content Publisher takes working with content to a whole new level. As an editor you can see all changes at a glance and publish them. Changes of major revisions can be prepared and approved individually. Pages and related content and files are reliably transferred as well. You can also publish selected page trees to the live server.

Editing pages can be structured into a multi-step workflow, thus editing, reviewing, and publishing can be separated into distinct roles. The modern user interface facilitates intuitive handling without excessive training.


If you have questions please have a look at the FAQs first. If your question is not listed try to find your answer in the documentation. You can ask questions (no support!) in the #ext-in2publish Slack channel on but there is no warranty. If you need support you can contact in2code.

Technical note

The content publisher basically requires two TYPO3 instances. A staging and a live instance. Editors work solely on the stage server. They also have a backend module to manage pages and files and their publishing status. This means that backend access to the live server is not required anymore. The data transfer between the two servers is secured by encrypted connections and allows only unidirectional system access from stage to live.

Data from the live server is only transferred upon explicit request from the stage server. This also means that the stage server can be placed inside the private company intranet while the live server is accessible throughout the internet. The same TYPO3 extension is installed on both servers. So both servers only differ in configuration. This has the great advantage that an existing deployment can be used for both systems at once.

See for more details:



Example overview module with details


Side by side comparison between stage and live


Installation support by a lot of tests


Example workflow module (part of the enterprise version)


Example workflow feature (part of the enterprise version)


Browser notifications after asynchronous publishing (part of the enterprise version)


composer require in2code/in2publish_core

Easy installation via composer. See documentation for a step by step manual


Version changelog

See: Changelog