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
Once #32980 is done and the controller is available we can then remove the principle based on RouteNotFoundException in the index.php file, any URL even the legacy ones would be handled via Symfony
Some generic route mapping will need to be found to catch the legacy URLs, the URL should not change to avoid breaking changes, it's just that the layout would now be handled by Symfony. This will simplify the work about authentication by Symfony a lot since after this ALL the pages (including the legacy ones) would be handled by the framework.
fabienvallon
changed the title
Once this controller is available we can then remove the principle based on RouteNotFoundException in the index.php file, any URL even the legacy ones would be handled via Symfony Some generic route mapping will need to be found to catch the legacy URLs, the URL should not change o avoid breaking changes, it's just that the layout would now be handled by Syfony. This will simplify the work about authentication by Symfony a a lot since after this ALL the pages (including the legacy ones) would be handled by the framework.
Replace legacy Layout ( Part 2)
Jun 22, 2023
jolelievre
changed the title
Replace legacy Layout ( Part 2)
Handle legacy page display via the Sylfony controller automatically and systematically
Jun 22, 2023
jolelievre
changed the title
Handle legacy page display via the Sylfony controller automatically and systematically
Handle legacy page display via the Symfony controller automatically and systematically
Jun 22, 2023
fabienvallon
changed the title
Handle legacy page display via the Symfony controller automatically and systematically
[Replacing layout in legacy pages] Handle legacy page display via the Symfony controller automatically and systematically
Jul 7, 2023
jolelievre
changed the title
[Replacing layout in legacy pages] Handle legacy page display via the Symfony controller automatically and systematically
Handle legacy page display via the Symfony controller automatically and systematically
Jul 10, 2023
Blocked by #32980
Description
Once #32980 is done and the controller is available we can then remove the principle based on
RouteNotFoundException
in theindex.php
file, any URL even the legacy ones would be handled via SymfonySome generic route mapping will need to be found to catch the legacy URLs, the URL should not change to avoid breaking changes, it's just that the layout would now be handled by Symfony. This will simplify the work about authentication by Symfony a lot since after this ALL the pages (including the legacy ones) would be handled by the framework.
Example:
Acceptance test
UI tests work fine with symfony layout enabled even on legacy pages
Blocked by #32980
The text was updated successfully, but these errors were encountered: