The start of the custom Easyadmin repository was made on top of Symfony 5.4. It was time for an uplifting. A peek in what was done to update to 7.2 and the small changes to custom easyadmin code linked to it.

Let’s continue our dive into the customization of Easy Admin listing page. We’ve first looked at the fields customization, then access restriction. Here, we want to explore the listing and its actions. In this last, out of three posts here, we’ll focus on how to define custom actions on the entity items.

Let’s continue our dive into the customization of Easy Admin listing page. We’ve first looked at the fields customization. Here, we want to continue exploring the listing and its specificities. In this second, out of three posts here, we’ll concentrate ourselves on how to define data access restrictions.

Let’s continue our dive into the customization of Easy Admin linked to Symfony. We’ve looked at update security on specific actions on the listing/index page. Here, we want to continue exploring the listing and its customizations. In this first, out of three posts here, we’ll concentrate ourselves on how to customize the rendering of the data in the listing.

As a first update of the Admin, let’s tackle the least original of all... handling Users… Not any logged in users should be able to update any users, more none of them should be allowed to do anything to any users, so let’s try to restrict the potential actions on our Users only to the Admins of the application.

In Symfony, the recommended admin backend is EasyAdmin. To illustrate the base capabilities of the tool, an EasyAdmin demo repository has been setup for anyone to look at and experience how to use EasyAdmin. The objective in this series of articles (supported by a live repository) is to illustrate less common, but still useful, features of EasyAdmin.

In my Symfony 5.3 (and upwards) projects, to enable some data in my tables for raw development and for the testing, I use Hautelook/Alice Bundle

I have the need on my symfony applications to run, in PHPStorm, commands in debug mode (after some test failures for instance ;-)) while having a Vagrant development environment.

In my Symfony 4/5 projects, to enable some data in my tables for raw development and for the testing, I use Hautelook/Alice Bundle