Configuring Fields

Hey Sébastien J.!

Thanks for reporting that! I have no idea what went wrong, but I basically "refreshed" the video on our end, and it seems to be working now. Please let me know if you still have any problems!

Cheers!

Hey Javier,

That's awesome news! Yeah, most fields are clear base on their names, but having more detailed docs on them will definitely help newcomers. And yeah, PHP autocompletion helps a lot too.

Thanks for the head ups :)

Cheers!

Yay PHP config!!!

Hey CDesign,

Thank you for raising this up and providing the link to the PR that explains the reasons behind of this change. Yeah, it makes sense

Cheers!

Hey Hubert,

Yes, it will be covered a bit later in this course, so stick with us :) For now, it's more like simple field rendering and acquaintance with field types :)

Thank you for your patience!

Cheers!

Hey Eduard,

Yeah, most probably you also need to execute bin/consoel assets:install command. I think that should do the trick and make some JS available for you. If still nothing, check the Console tab in the Google Chome dev tools, I bet it contains some errors that may hint you what else you need to do.

Cheers!

Thank you very much for the quick reply.

I have just found the cause. The code fields are inside a CollectionField. I had to add the entries for CSS and JS files from CodeEditField to the CollectionField so that the testarea is replaced by the code editor. I should watch this SymfonyCast more carefully ))
This code solved the problem:

yield CollectionField::new('codeCollection')
    ->addJsFiles(Asset::fromEasyAdminAssetPackage('field-code-editor.js')->onlyOnForms())
    ->addCssFiles(Asset::fromEasyAdminAssetPackage('field-code-editor.css')->onlyOnForms())

Hey Eduard,

I'm glad to hear you found the problem! And thanks for sharing the solution with others :)

Cheers!

Hey Gianluca-F,

Did you try this code in your EA 3 version? It might work I suppose because I see that v3 still has support, though it might be only security fixes support though. But it does not work - not sure then, try to ask this question on the bundle's repo, maybe someone who tried this will give you some tips how to achieve it, because I can't give you any tips about it, never do this before.

But if it does not work out of the box with the. TextEditorField - I'd recommend you to use simple TextField and attach any JS editor you love to it, you can easily add JS fields to specific CRUD controllers.

Cheers!

Hi Victor,
I have installed CKEditorBundle, I have created a new CustomField that use CkEditorType and I'm using it; it is awsome and works like a charm :-)

Thanks !

I have installed CKEditorBundle - ran the configuration but still cannot get it to display - going out my mind here :/

try to add these lines to

config/packages/fos_ckeditor.yaml

twig:
    form_themes:
        - '@FOSCKEditor/Form/ckeditor_widget.html.twig'

Hi GianLuca finally managed it, after installing CK Editor bundle & installing it I created a new Custom Field class called ContentField

<?php

namespace App\EasyAdmin;

use EasyCorp\Bundle\EasyAdminBundle\Contracts\Field\FieldInterface;
use EasyCorp\Bundle\EasyAdminBundle\Field\FieldTrait;
use FOS\CKEditorBundle\Form\Type\CKEditorType;

class ContentField implements FieldInterface
{
    use FieldTrait;

    public static function new(string $propertyName, ?string $label = null, ?string $configName = null): self
    {
        return (new self())
            ->setProperty($propertyName)
            ->setLabel($label)
            // this template is used in 'index' and 'detail' pages
            ->setTemplatePath('@EasyAdmin/crud/field/text_editor.html.twig')
            // this is used in 'edit' and 'new' pages to edit the field contents
            // you can use your own form types too
            ->setFormType(CKEditorType::class)
            ->setFormTypeOptions(
                [
                    'config'=>[
                        'toolbar' => 'full',
                        'extraPlugins' => 'templates',
                        'rows' => '20',
                    ],
                    'attr' => ['rows' => '20'] ,
                ])
            ->addCssClass('field-ck-editor');
    }
}

And then in my PagesCrudController added configureCrud function to call my twig template

    public function configureCrud(Crud $crud): Crud
    {
        return $crud
            ->addFormTheme('@FOSCKEditor/Form/ckeditor_widget.html.twig')
            ;
    }

And finally called the CustomField I created above in the configureFields function

         yield ContentField::new('pageCopy', false)
            ->setColumns('col-sm-12 col-md-12 col-lg-12');

Hey Paul,

Well done! And thanks for sharing your solution with others, it might be helpful :)

Cheers!

Hey Gianluca-F,

That's awesome! And thank you for letting us know that it works for you well this way, I bet some users might be interested in it as well :) Yep, EA has some tools out of the box, but sometimes you can do extra work to make it even better for your project like with the CKEditor integration you made, well done!

Cheers!

Autoresponding myself :)))

The solution is:

DateField::new('myEntityDate', 'date')
->formatValue(function ($value, $entity) use ($helper) {
return $helper->someFunction($entity, $value);
}),

The second parameter of the closure seems to be the entity object.

Hey Kershin

Yep! You're right, the second argument of the closure gives you the entity, but be aware that the $entity argument may be null, so you may want to code defensively

Cheers!

Hello Diego !
Thanks for your answer.
In which case the $entity argument could be null ? (in index & detail views)
Regards,

Hey Tomáš S.!

Ah, then this is a "validation" trick: you need to make sure that you show the user a validation error if A & B are empty OR if A & B are both NOT empty. This actually has nothing to do with EasyAdmin, which is great! EasyAdmin simple "runs your entity's validation rules". And so, if we can get the validation rules setup on your entity correctly, it will just work :).

For this, I would use the Callback constraint: https://symfony.com/doc/cur...

This allows you to write a function in your entity that contains the exact validation logic you need. The only thing you'll need to decide is which field to attach the error to (field A or field B) in case they have filled out neither or both.

Let me know if this helps :).

Cheers!