PHPackages                             devskio/content-element-registry - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility &amp; Helpers](/categories/utility)
4. /
5. devskio/content-element-registry

ActiveTypo3-cms-extension[Utility &amp; Helpers](/categories/utility)

devskio/content-element-registry
================================

Content element registry - helper for registering Typo3 content elements

13.0(11mo ago)02.7k↓33.3%GPL-2.0-or-laterPHP

Since Aug 22Pushed 11mo ago1 watchersCompare

[ Source](https://github.com/devskio/content-element-registry)[ Packagist](https://packagist.org/packages/devskio/content-element-registry)[ RSS](/packages/devskio-content-element-registry/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependencies (2)Versions (7)Used By (0)

[![](https://github.com/devskio/content-element-registry/raw/master/Resources/Public/Icons/Extension.svg?sanitize=true)](https://github.com/devskio/content-element-registry/raw/master/Resources/Public/Icons/Extension.svg?sanitize=true) Content element registry
====================================================================================================================================================================================================================================================================

[](#-content-element-registry)

Typo3 extension simplify process of creating new content elements (CE) in [Typo3 way](https://docs.typo3.org/typo3cms/extensions/fluid_styled_content/7.6/AddingYourOwnContentElements/Index.html)

Install
-------

[](#install)

Install extension via composer `composer req devskio/content-element-registry` and activate it in Extension module

Setup
-----

[](#setup)

After activating extension, you have to define your Content elements configuration classes. It can be done in two ways:

1. By defining paths in extension configuration (aka *extConf*). Can contain comma separated list of paths to directories **Example:** `EXT:your_ext_1/Classes/ContentElements/,EXT:your_ext_2/Classes/ContentElements/`[![](./Resources/Public/Images/ExtConfSettings.png)](./Resources/Public/Images/ExtConfSettings.png)
2. By registering Listener in `Services.yaml` of your extension as follows:

```
  Vendor\Extension\EventListeners\ContentElementRegistryListener:
    tags:
      - name: event.listener
        identifier: 'contentElementRegistryListener'
        event: Devsk\ContentElementRegistry\Events\ContentElementRegistryClassEvent
```

Method `Vendor\Extension\EventListeners\ContentElementRegistryListener` can looks like this:

```
