MetaModels core

Installs: 50 381

Dependents: 70

Suggesters: 0

Security: 0

Stars: 95

Watchers: 20

Forks: 42

Open Issues: 104


2.2.9 2023-05-01 22:41 UTC


Build Status Latest Version tagged Latest Version on Packagist Installations via composer per month


So what are MetaModels?

MetaModels are data models you can configure in the Contao Backend. Every MetaModel consists of various attributes of certain data types (attribute types are available as extensions and get registered upon installation).

To present the data on the screen (i.e. website, RSS feed, etc.), you define render settings for the MetaModel which define how the various attribute output shall look like (image sizes, use light boxes, etc.).

Filtering data in list views needs configuration of filter settings. Filter settings are a very complex topic, as they can be nested (AND/OR conditions i.e.) and be of various nature.

Before you start it is helpful to look at the MetaModels manual. There you will find actual information about the usage and the installation.

How to use it.


You can install MetaModels core with Contao Manager - search "metamodels/core" - or you can use composer

php web/contao-manager.phar.php composer require metamodels/core

Then add all the necessary attributes, filters or MetaModel extensions.

For the first evaluation of the possibilities of MetaModels you can also use metamodels/bundle_start, which installs some attributes and filters.

Please do not forget to perform the migration of the database!


Feel free to contribute the MetaModel Documentation in EN or DE



Metamodels are the replacement for the famous Catalog extension for Contao CMS.

As the catalog extension was growing too complex to maintain and most support for extendability was rather hacky, we decided it was time to take everything we learned during the development of Catalog 1 and Catalog 2 to provide you with Catalog 3 which shall be even more flexible and very easy to extend with own classes.

As development did go on nicely, we realized that an easy migration from Catalog to the new version will not very likely be possible both in implementation and learning curve but that this will be a very own and unique extension resembling only of the name with it's ancestor. Therefore, we rebranded everything as "MetaModels".

Who did it?

See the file.

Third Party Licenses:

Icons: This software uses the Fugue Icons