Diem uses the excellent symfony admin generator. But with some additions.
Diem is smart enough to write the generator.yml file for you. When you generate a new module with
php symfony dm:setup
The admin module is created, with a quite good generator.yml.
Later, if you add fields to the model, Diem will not add the fields to the generator.yml, because it may override your changes. So, if you want Diem to regenerate a generator.yml from the current model, use
php symfony dmAdmin:generate --clear=myModule
If you override a plugin model in your schema.yml, the admin module will not be generated in your project. You have to copy manually the plugin generator.yml:
into your project, in
And add the missing fields manually, as you would do in a normal symfony application.
Diem admin generator comes with more features than the symfony one.
One symfony feature has been dropped : the filters. It has been replaced by a single-field search engine, that searches into all model fields.
Diem admin interface is heavily inspired by the Total Usability Blog and the Gmail interface.
config: fields: url: is_link: true title: is_big: true body: markdown: true
When a field is marked as is_link, it becomes droppable.
When a database field contains a link, it's better to declare it in the schema.yml. This way, not only the admin generators knows how to deal with it, but the whole project too.
Diem admin forms are displayed in two columns.
When a field is marked as is_big, it uses the two columns.
When a textarea is marked as markdown, it is transformed into a markdown editor with an ajax preview.
When a database field contains markdown text, it's better to declare it in the schema.yml. This way, not only the admin generators knows how to deal with it, but the whole project too.
With symfony only, we can't sort list results by a partial column.
With Diem it's made possible if the partial has the same name than a database field.
For example suppose we have a "Product" model, with a "price" field.
We will create the "_price.php" template to show exclusive of taxes and inclusive of taxes prices.
When clicking on the list "_price" column, list will be sorted using the "price" field.
To add versioning to your model, declare which fields are versionned on the
Post: actAs: DmVersionable:
If your model is translatable, use Doctrine nested behaviors to enable versioning on i18n fields:
Post: actAs: I18n: fields: [ title, body ] actAs: DmVersionable:
Diem will automatically add an history button on the post admin form. In the history interface, you can:
Questions and Feedback
If you need support or have a technical question, you can
The documentation is hosted on GitHub. Feel free to submit issues and patches!