SonataAdminBundle | The missing Symfony Admin Generator | Web Framework library

It appears to be possible to simply put a string / template to the list view, but is the same possible to the edit view of an entity in Sontata Admin 4?

I found https://docs.sonata-project.org/projects/SonataAdminBundle/en/4.x/reference/templates/#configuring-templates, but it only allows does not give access to the form itself. This is the include I found in base_edit.html.twig:

From version 3.102.0 of SonataAdminBundle a lot of methods in AbstractAdmin are marked as final. The most important (in my opinion) "checkAccess" and "hasAccess" methods are also marked as "final" and cannot be overwritten in Admin classes any more to handle access to actions on my own. How to handle cases when I want restrict access to some actions based on state of object?

For example I have "Task" entity:

I am trying to set up a simple CMS using Sonata Admin Bundle. I use composer to add sonata-project/admin-bundle and sonata-project/doctrine-orm-admin-bundle to an empty git repository, then follow the rest of the directions on https://sonata-project.org/bundles/admin/3-x/doc/getting_started/installation.html

Now I visit http://localhost/admin/dashboard, which the instructions say should give me a blank dashboard. Instead, I get a ServiceNotFoundException, stating:

The service "sonata.admin.menu.group_provider" has a dependency on a non-existent service "security.authorization_checker".

Is there a bundle or configuration that I need to install/add in order to fix this?

===

When I run bin/console debug:container security.authorization_checker I get the following output:

In CheckExceptionOnInvalidReferenceBehaviorPass.php line 86:

The service "sonata.admin.menu.group_provider" has a dependency on a non-existent service "secur ity.authorization_checker".

===

Here is config/packages/sonata_admin.yaml:

I am in the process of migrating a project from Symfony 2.8 to 3.4.

In this project , I used sonataUserBundle as a dependency ( before migrating ) which unfortunately does not work in Symfony 3.

So, I tried to use SonataAdminBundle with FosUserBundle and I removed the SonataUserBundle dependency.

After removing "sonata_user" configuration from config.yml file , I had the following exception:

An exception has been thrown during the rendering of a template ("Unable to generate a URL for the named route" admin_del_user_user_edit "as such route does not exist.").

So my question is : is it possible to remove sonataUserBundle and use only sonataAdminBundle and FosUserBundle in order to build a back office?

How can I resolve the routeNotFoundException ?

I'm trying to integrate SonataNewsBundle in Symfony 4.4.

The CKEditor is not showing in the "Content" field for the news post. I've read through probably all of what's to be found online and couldn't find a way to solve this problem.

fos_ck_editor.yaml:

I am currently working on a website and I have to use Sonata Admin for the back office. I am upgrading the project from symfony 3 to symfony 4 and I have a problem when I try to filter the instantiated entities.

I configured a filter that way :

I'm trying to set up a Symfony 3.4 project on an Apache (2.4.25) server. However, I'm facing issues with the rooting.

The application works smoothly with the built-in server (all routes). However, on Apache server, I'm unable to access the login page. The /login path is automatically change to web/login and result in:

No route found for "GET /web/login/"

Since the application (and the routing) is working with the built-in server, I suspect an issue in the apache configuration. In the built-in server, the /login isn't rewrite.

Note:

• All the others routes reachable without being logged in are working.
• Symfony 3.4
• Apache 2.4.25

Here the Apache files:

.htaccess in the web folder:

I've got an error for some time now when I try to add filters to an Admin. There are two entities: Client and Order.

In the OrderAdmin file, the following filters work:

I have a web application currently running on Symfony 4.3.5 without any problems.

I call "php composer.phar update" in my project directory. Composer starts to download and upgrade packages to version 4.4 and finally fails with