Skip to content
in2publish Community Version
Branch: develop
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
Classes [BUGFIX] Respect definition keys when merging default config values Jul 4, 2019
Configuration [BUGFIX] Detect the cli dispatcher automatically, add an override option May 24, 2019
Documentation [DOCS] Add a minimal example to implement custom tasks Jun 17, 2019
Resources [BUGFIX] Detect the cli dispatcher automatically, add an override option May 24, 2019
Tests [COMMENT] Update all copyright notices from docblock to comment Feb 28, 2019
.editorconfig [DEV] Replace jshint and jscs with eslint Mar 26, 2018
.eslintrc [DEV] Replace jshint and jscs with eslint Mar 26, 2018
.gitattributes [DEV] Replace jshint and jscs with eslint Mar 26, 2018
.gitignore [FEATURE] Import the public part of the original code Aug 26, 2016
.travis.yml Update .travis.yml Feb 28, 2019
CHANGELOG.md [DOCS] Update changelog Jun 25, 2019
CONTRIBUTING.md [COMMENT] Update all copyright notices from docblock to comment Feb 28, 2019
LICENSE
README.md [!!!][FEATURE] Rewrite configuration management to extensible structure Mar 23, 2018
composer.json [META] Set the branch alias version number to 8.2.x-dev May 28, 2019
ext_conf_template.txt
ext_emconf.php
ext_localconf.php [BUGFIX] Delay in2publish_core configuration until autoload informati… Mar 18, 2019
ext_tables.php [BUGFIX] Add test to detect the missing default FAL storage May 6, 2019
ext_tables.sql [!!!][REFACTOR] Rename log table to tx_in2publishcore_log Mar 23, 2018
ext_typoscript_setup.txt [BUGFIX] Include the Plugin definition as reference because it might … May 29, 2017
phpunit.xml.dist [DEV] Set correct phpunit schema version Sep 21, 2018

README.md

in2publish_core - Content publisher for TYPO3

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)

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.

Questions

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 typo3.slack.com 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:

Screenshots

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)

Installation

composer require in2code/in2publish_core

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

Documentation

Version changelog

See: Changelog

You can’t perform that action at this time.