Download the PHP package in2code/in2publish_core without Composer

On this page you can find all versions of the php package in2code/in2publish_core. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package in2publish_core

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:

Support

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

Description

The Content Publisher for TYPO3 is an extension that allows the separation of TYPO3 into an editorial system and a live system. This separation allows editors to prepare and test their content independently from the live system. When the new content is ready to be published, it is transferred to the live system by the Content Publisher with a single click. Even embedded images and files are reliably transferred. The Content Publisher thus takes working with content to a new level. Content can be compared with the live system before publication and pages with changes are highlighted in color.

The Content Publisher can transfer entire pages or, in the Enterprise Edition, individual content elements. It is highly extensible and configurable and supports all TYPO3 features and 3rd party extensions, as long as they provide correct TCA.

The Enterprise Edition extends the Content Publisher with a large number of features, such as workflows to organize pages and individual content types in the editing process, workflow assignment, workflow email notification, workflow colors in the page tree, publishing permissions, limiting publishing to languages, support for Solr, EXT: fal_securedownload, EXT:rte_ckeditor_image, Remote Cache Control, Fire and Forget and more.

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

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

Testing

Hint: https://youtrack.jetbrains.com/issue/WI-74556/PHPUnit-settings-are-not-configured#focus=Comments-27-8185787.0-0

All versions of in2publish_core with dependencies

PHP Build Version
Package Version
Requires php Version ^7.4 || ^8.0
ext-json Version *
ext-pdo Version *
ext-zip Version *
typo3/cms-core Version ^11.5 || ^12.4
symfony/yaml Version ^v5.4 || ^v6.3
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package in2code/in2publish_core contains the following files

Loading the files please wait ....