You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By the v1.8 of Sylius, the SyliusAdminBundle routes prefix can be modified thanks to the use of an environment variable (Sylius/SyliusAdminBundle@eb93fc1).
However, this is possible as long as you don't use plugins with admin routes. Many of these, in fact, define, in the routing configuration file, the admin prefix statically as part of the path (like this). Others don't use the prefix (like this) and let the user define the prefix as here. This second solution will be profitable because you could use the %sylius_admin.path_name% as a prefix.
What do you think about these? IMHO we should define a standard compatible with Sylius < 1.8, and for example, updates the routes.yaml file by using the correct prefix parameter or admin if is not defined.
The text was updated successfully, but these errors were encountered:
By the v1.8 of Sylius, the SyliusAdminBundle routes prefix can be modified thanks to the use of an environment variable (Sylius/SyliusAdminBundle@eb93fc1).
However, this is possible as long as you don't use plugins with admin routes. Many of these, in fact, define, in the routing configuration file, the admin prefix statically as part of the path (like this). Others don't use the prefix (like this) and let the user define the prefix as here. This second solution will be profitable because you could use the %sylius_admin.path_name% as a prefix.
What do you think about these? IMHO we should define a standard compatible with Sylius < 1.8, and for example, updates the routes.yaml file by using the correct prefix parameter or admin if is not defined.
The text was updated successfully, but these errors were encountered: