Download the PHP package firegento/magento2-content-provisioning without Composer

On this page you can find all versions of the php package firegento/magento2-content-provisioning. 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 magento2-content-provisioning

FireGento Magento 2 Content Provisioning

This module was developed during a Magento Hackathon organized by FireGento e.V. (https://firegento.com/).

ℹ️ Maintenance

This module is maintained by TechDivision. Therefore, there we created a mirror repository, which allow us to run automated quality checks on our internal infrastructure for this module. Please see https://gitlab.met.tdintern.de/techdivision-public/m2-content-provisioning for details. Please feel free to contact us, if you have questions regarding the repository structure or mirroring.

Build-Status (develop branch)

pipeline status

The idea behind this module

It is a common requirement, that some parts of content (like CMS pages or blocks) need be deployed within a release. There are content entries, which should be maintained by code all the time and some content just needs delivered one time to each system.

In most cases such requirements will be solved by setup scripts (or setup patches), which is possible way there is no chance to declare the responsibility for each content entity.

This module allows you to declare such content entries via XML file and ensures, that this declaration will be applied to database on each setup:upgrade run.

Install with composer

How it works

After installing this module you can create your own content_provisioning.xml in each of your modules.

Example configurations

Minimal configuration for a page

Full configuration for a page

Minimal configuration for a block

Full configuration for a block

Some explanation

key-Attribute

The key attribute is required in order to merge all content provisioning configurations across all modules. It is like the name attribute for layout blocks...

You could use identifier - or?

No, identifier is not unique since the same identifier can be used for multiple store views.

maintained-Attribute

With this attribute you define whether this content should be applied every time or even only once. Is the value false the content will only be persisted, if there is no identifier for the defined stores present in database.

content-Node

This node provide THE content for your page or block. It can be added as node value in a CDATA block or as a file path, which is relative to your Magento instance or prefixed by a module namespace. In order to use files you need to add the type="file" attribute to the content node.

stores-Node

This node is optional. If it is not defined, the block or page will be applied to all stores. A "maintained" entry will also be applied to stores, which will be created in the future after re-running setup:upgrade command. You can also use the 'wildcard' * in order to define that the content should be applied to all stores.

media_directory-Node (since version 1.2.0)

Specifies the directory for media files. Each used media file in the content and present in media source directory will be copied to Magento's pub/media directory. Sub-directory structure should be same like inspected it to be in pub/media. Only existing and used media files will be copied.

Executing integration tests on local environment

Console Commands

Issues and planned features

See issues to see what's planed next: https://github.com/magento-hackathon/m2-content-provisioning/issues Feel free to add your ideas there.

Changelog

See changelog file

Extensions for this extension ;)

For magenerds/pagedesigner there is an module, which extends this content provisioning module: techdivision/pagedesigner-content-provisioning .

All versions of magento2-content-provisioning with dependencies

PHP Build Version
Package Version
Requires ext-dom Version *
magento/framework Version >=100.1
magento/module-cms Version >=101.0
magento/module-widget Version >=100.1
magento/module-backend Version >=100
magento/module-ui Version >=100
magento/module-store Version >=100
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 firegento/magento2-content-provisioning contains the following files

Loading the files please wait ....