MetaModels

With version 2.2 we want to make MetaModels for the new LTS 4.9 of Contao compatible and add more features - this includes adaptations to the DCG.

For financing, we have again an "early adopter" program (EAP) which gives immediate access to the current MM 2.2-dev. The grant for access via EAP should be at least 350€ (excl. VAT)*1. The access is again valid for one project.

For more information about the details please send an e-mail to mail@metamodels.me

 

*1: Invoice incl. VAT will be issued - with EU-Tax-ID in net; donor will be named and linked on request

With this feature, it is possible to sort files/images manually in the backend for frontend display. The feature is also available for multilingual selection and was tested with MM core a15 and DCG b39.

For this fundraising, the MM developers “donated” 1/3 of the total effort so that the remaining amount of the fundraising is now 3,245.00 €.

As soon as this amount is collected, the feature will be activated.

For all users, who would like to have this feature before the fundraising is completed, there are the following possibilities:

• Donation of at least 10% of the remaining amount
• An equivalent amount of work for the MetaModels-Project
• An equivalent source code for a feature or bugfix

Update 30.10.2018

Our early adopter program (EAP) will be extended until the transfer to Gitlab is completed.  For the transfer, some adjustments are required – the exact date of the release is still pending.

For access to the protected repositories of MM 2.1 before the transfer is completed, please use our EAP, which starts at a donation amount of 500€.

For more information, please contact mail@metamodels.me

~~~~~~~~~~~~~~~~~~

With the release of Contao 4.4 at the Contao conference, there were obviously discussions about MetaModels and Contao 4.

As reported in the may news, the plan is to develop MetaModels 3 using the features of Symfony and discard old “ballast”. But this means also a long development time.

There is agreement for this approach, but also the community asked for a faster solution to run MetaModels with Contao 4. The MM Team discussed this issue closely and tried to come up with a fast solution.

Therefore, we will develop a MetaModels 2.1 as an intermediate step which will work with Contao 4 (but not with Contao 3.5). The data base structure will be similar like MM 2.0. So a migration from 2.0 to 2.1 is possible with little effort.

The work is already in progress to estimate the (time) requirements. The development of the Version 2.1 will also build the foundation for Version 3.0.

For the implementation of MM 2.1, we started a fundraising campaign with a goal of 15,000 €. Depending on the progress of the fundraising, the implementation could start end of September/beginning of October 2017 and be finalized in November.

As already known from Catalog, Frontend editing shall also be possible with MetaModels, this means, website members may create, edit and delete items from MetaModels in the frontend of the website.

MetaModels is going to enhance and improve all current available functionality known from Contao and Catalog regarding Frontend editing with an unique approach to further develop the central DC_General component. With this entirely new approach we want to move on new ground, as Contao does not provide any generic Frontend editing at all so far, we are taking the challenge of reinventing the wheel. Of course the enhancements of DC_General are available to other extensions aside from MetaModels as well. Therefore the Contao community as a whole will be able to benefit from this feature.

The involved changes are major refactoring in DC_General and adapting the core and attributes to the needed changes imposed by this refactoring. We also might have to create some new widgets that are not yet available in the Frontend.

Everyone knows the possibilities to keep the input screens clean and well arranged. Contao provides, in addition to CSS classes, so called "subpalettes". These allow to display certain input fields only after a checkbox has been ticked. This functionality is already part of MetaModels.

What's missing, is the same feature being also applied to select widgets, to display certain input fields only, when a certain value has been selected. This would provide an even more simple way to hide non relevant input fields from the user an display them only as needed.