Chapters

23 Chapters | 2:26:29 |

01

Installation and First Admin

5:56
02

Design Config & Security Setup

4:16
03

Views & entities Config

5:57
04

Actions Config

7:06
05

Configuring the List Fields

4:12
06

More about List Field Types

6:06
07

DQL Filtering & Sorting

5:19
08

Customize all the Templates!

5:05
09

Dynamically Remove the delete Action Link

7:56
10

Customize Template for One Field

1:53
11

Form Field Customization

6:15
12

The Autocomplete Field

1:50
13

CollectionType Field

5:51
14

Custom Fields with JavaScript

4:15
15

Form Theming For a Completely Custom Field

8:52
16

Adding a Custom Action

10:32
17

Override Controllers

7:11
18

Event Hooks

6:15
19

Conditional Actions

9:30
20

CSV Export

11:48
21

Tweaking the Form Layout

9:06
22

Dashboard & Menu Customizations

4:02
23

Customizing the Menu

7:16

This tutorial has a new version, check it out!

> Symfony 3 > EasyAdminBundle v1 for an Amazing Admin Interface

Buy Access to Course

21.

Tweaking the Form Layout

|

Autoplay

Keep on Learning!

If you liked what you've learned so far, dive in! Subscribe to get
access to this tutorial plus video, code and script downloads.

Start your All-Access Pass

Buy just this tutorial for $8.00

Previous Chapter

Next Chapter

With a Subscription, click any sentence in the script to jump to that part of the video!

Login Subscribe

Login or register to check out the script

9 Comments

Sort By

Login or Register to join the conversation

Tim-K 5 years ago edited

Hi, thanks for the tutorial, which helped me a lot also in using EasyAdmin3.
But I struggle to implement a "two column" layout.

This is "reducing" the width correctly

<br />public function configureFields(string $pageName): iterable<br />{ <br />[...]<br />yield FormField::addPanel('Some Headline 1')->setCssClass('col-sm-6')<br />yield FormField::addPanel('Some Headline 2')->setCssClass('col-sm-6')<br />[...]<br />}<br />

but the blocks are not next to each other. Do you have a tip what I can do?

|

weaverryan SFCASTS Tim-K 5 years ago

Hey @Tim!

> Hi, thanks for the tutorial, which helped me a lot also in using EasyAdmin3

Happy to hear it's useful even if it's not WAY old :).

> but the blocks are not next to each other. Do you have a tip what I can do?

I'm not familiar with the HTML and layout that EasyAdmin 3 uses. For this to work, in the rendered HTML, both those elements would need to be inside their own <div class="row"> element. What do you see in the rendered HTML?

Cheers!

|

amcastror 8 years ago

Hi, thanks for the tutorial.

You said that we were going to fix the order later (for the slug field). Is that in another chapter of the EasyAdminBundle tutorial?

|

Victor SFCASTS amcastror 8 years ago

Hey Matias,

Yes, it should be in further chapters :)

Cheers!

|

Kaizoku 8 years ago

Hi there !
Do you think it's possible to hide a whole group in the 'new' view ?

Regards.

|

weaverryan SFCASTS Kaizoku 8 years ago edited

Hey Kaizoku!

Sorry for the slow reply! Hmm, I doubt this is possible :/. The groups don't even have named keys in yml, so there would be no way to even do a -groupName type of thing to remove it :/. I think, unfortunately, that your best option is to specify new and edit forms independently (the unfortunate part is the duplication). I had another possible idea, which was to use a custom form class for the entire form, and build the fields & groups yourself (and then you could just some PHP logic), but that's not currently possible.

Cheers!

|

Kaizoku weaverryan 8 years ago

Thanks for the answer.
Actually it's not a big deal as I'm removing the fields with a -field, so I just have the panel title with and empty body.
I guess I can use some JS to hide the panel, but it's really not important.

|

Victor SFCASTS Kaizoku 8 years ago edited

Hey Kaizoku ,

Yeah, JS can do the trick, but I bet it's possible to override some templates and hide it on the backend level instead.

Cheers!

|

IvanPuntiy Victor 7 years ago edited

This worked for me:

            form:
                fields:
                    - { type: group, css_class: col-sm-6, label: Basic Information }
                    - name
                    - speciesCount
                    - { property: firstDiscoveredAt, type_options: {widget: single_text} }
                    - { property: subFamily, type: easyadmin_autocomplete }
                    - { type: section, label: Optional }
                    - { property: funFact, type: textarea, css_class: js-markdown-input }
                    - isPublished

                    - { type: group, css_class: col-sm-6, label: Studied by ... }
                    -
                        property: genusScientists
                        type: text
                        type_options:
                            mapped: false
                            attr: { class: js-scientist-field }
            edit:
                fields:
                    -
                        type: group
                        css_class: col-sm-6 new-row
                        label: Identification
                        icon: id-card-o
                        help: For administrators
                    -
                        property: id
                        type_options: { disabled: true }
                    -
                        property: slug
                        help: Unique auto-generated value
                        type_options: { disabled: true }
            # new:
            #     fields:
            #         - '-id'
            #         - '-slug'```

But, of course, it forces the separated groups to be at the end of the form.

|

This tutorial is built on an older version of Symfony & EasyAdminBundle. Many of the concepts are the same, but you can expect major differences in newer versions.

Symfony 3 EasyAdminBundle 1

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=5.5.9",
        "symfony/symfony": "3.3.*", // v3.3.18
        "doctrine/orm": "^2.5", // v2.7.2
        "doctrine/doctrine-bundle": "^1.6", // 1.10.3
        "doctrine/doctrine-cache-bundle": "^1.2", // 1.3.5
        "symfony/swiftmailer-bundle": "^2.3", // v2.6.7
        "symfony/monolog-bundle": "^2.8", // v2.12.1
        "symfony/polyfill-apcu": "^1.0", // v1.17.0
        "sensio/distribution-bundle": "^5.0", // v5.0.25
        "sensio/framework-extra-bundle": "^3.0.2", // v3.0.29
        "incenteev/composer-parameter-handler": "^2.0", // v2.1.4
        "knplabs/knp-markdown-bundle": "^1.4", // 1.7.1
        "doctrine/doctrine-migrations-bundle": "^1.1", // v1.3.2
        "stof/doctrine-extensions-bundle": "^1.2", // v1.3.0
        "composer/package-versions-deprecated": "^1.11", // 1.11.99
        "javiereguiluz/easyadmin-bundle": "^1.16" // v1.17.21
    },
    "require-dev": {
        "sensio/generator-bundle": "^3.0", // v3.1.7
        "symfony/phpunit-bridge": "^3.0", // v3.4.40
        "nelmio/alice": "^2.1", // v2.3.5
        "doctrine/doctrine-fixtures-bundle": "^2.3" // v2.4.1
    }
}

Previous Chapter

Next Chapter