in2code/in2publish_core

Content publishing extension to connect stage and production server

6.0.2 2017-12-04 13:35 UTC

README

Latest Stable Version Build Status Latest Unstable Version License Codacy Badge

Introduction

Content Publishing in TYPO3 - the easy way:

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

68747470733a2f2f7777772e696e32636f64652e64652f66696c6561646d696e2f636f6e74656e742f696d616765732f70726f64756b74652f636f6e74656e747075626c69736865722f636f6e74656e745f7075626c69736865725f73637265656e73686f7430315f707265762e706e67

Description

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.

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:

Screenshots

68747470733a2f2f7777772e696e32636f64652e64652f66696c6561646d696e2f636f6e74656e742f696d616765732f70726f64756b74652f636f6e74656e747075626c69736865722f636f6e74656e745f7075626c69736865725f73637265656e73686f7430345f707265762e706e67

Example overview module with details

68747470733a2f2f626f782e6576657268656c7065722e6d652f6174746163686d656e742f3931353937342f38343732356662372d306233652d346334302d623532652d3239643736323037373762622f3236323430372d42617362745a41706c4c64395a4943492f73637265656e2e706e67

Side by side comparison between stage and live

68747470733a2f2f626f782e6576657268656c7065722e6d652f6174746163686d656e742f3931353936372f38343732356662372d306233652d346334302d623532652d3239643736323037373762622f3236323430372d3531536f644432447573624a355753342f73637265656e2e706e67

Installation support by a lot of tests

68747470733a2f2f626f782e6576657268656c7065722e6d652f6174746163686d656e742f3931353936352f38343732356662372d306233652d346334302d623532652d3239643736323037373762622f3236323430372d356e4866646c774a36744c4e507842692f73637265656e2e706e67

Example workflow module (part of the enterprise version)

68747470733a2f2f7777772e696e32636f64652e64652f66696c6561646d696e2f636f6e74656e742f696d616765732f70726f64756b74652f636f6e74656e747075626c69736865722f636f6e74656e745f7075626c69736865725f73637265656e73686f7430335f707265762e706e67

Example workflow feature (part of the enterprise version)

68747470733a2f2f626f782e6576657268656c7065722e6d652f6174746163686d656e742f3931353937302f38343732356662372d306233652d346334302d623532652d3239643736323037373762622f3236323430372d39335574513963506562304e435931652f73637265656e2e706e67

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

Installation

composer require in2code/in2publish_core

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

Documentation

Version changelog

See: Changelog