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
The legacy pages are rendered thanks to the Dispatcher from the index.php For now, the idea is to reverse what the legacy layout was. We need a LegacyController::legacyPageAction that would be used as a wrapper around the legacy controllers. In this controller the layout is rendered by Symfony and only the content at the center would be rendered by the legacy controller wrapped. The first step is to have this controller usable via a forced URL with the legacy controller passed as a parameter.
Like the generical Symfony layout is based on a Twig component, this legacy display should also be handled via a Twig component that will look like the generic one a lot except for a few exceptions that we need to anticipate (non-exhaustive list):
the theme used should be the default one not the new-theme
the loaded assets should match with the ones originally set via AdminController::setMedia(false)
... there may be some other things to consider / think about
Once the generic controller 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
The legacy pages are rendered thanks to the Dispatcher from the index.php For now, the idea is to reverse what the legacy layout was. We need a LegacyController::legacyPageAction that would be used as a wrapper around the legacy controllers. In this controller the layout is rendered by Symfony and only the content at the center would be rendered by the legacy controller wrapped. The first step is to have this controller usable via a forced URL with the legacy controller passed as a parameter.
Replacing layout in legacy pages ( part 1)
Jun 22, 2023
jolelievre
changed the title
Replacing layout in legacy pages ( part 1)
Replacing layout in legacy pages ( part 1) - Create generic Symfony controller able to display a legacy page
Jun 22, 2023
jolelievre
changed the title
Replacing layout in legacy pages ( part 1) - Create generic Symfony controller able to display a legacy page
Create generic Symfony controller able to display a legacy page
Jun 22, 2023
fabienvallon
changed the title
Create generic Symfony controller able to display a legacy page
[Replacing Legacy Layout] Create generic Symfony controller able to display a legacy page
Jul 7, 2023
fabienvallon
changed the title
[Replacing Legacy Layout] Create generic Symfony controller able to display a legacy page
[Replacing layout in legacy pages] Create generic Symfony controller able to display a legacy page
Jul 7, 2023
jolelievre
changed the title
[Replacing layout in legacy pages] Create generic Symfony controller able to display a legacy page
Create generic Symfony controller able to display a legacy page
Jul 10, 2023
MatShir
changed the title
Create generic Symfony controller able to display a legacy page
Create generic Symfony controller able to display a legacy page and Handle legacy page display via the Symfony controller automatically and systematically
Jan 12, 2024
MatShir
changed the title
Create generic Symfony controller able to display a legacy page and Handle legacy page display via the Symfony controller automatically and systematically
Create generic Symfony controller able to display a legacy page and its display via the Symfony controller automatically
Jan 12, 2024
MatShir
changed the title
Create generic Symfony controller able to display a legacy page and its display via the Symfony controller automatically
Create generic Symfony controller able to display a legacy page && its display via the Symfony controller automatically
Jan 12, 2024
MatShir
changed the title
Create generic Symfony controller able to display a legacy page && its display via the Symfony controller automatically
Create generic Symfony controller able to display a legacy page && handle its display via the Symfony controller automatically
Jan 12, 2024
Description
The legacy pages are rendered thanks to the Dispatcher from the index.php For now, the idea is to reverse what the legacy layout was. We need a
LegacyController::legacyPageAction
that would be used as a wrapper around the legacy controllers. In this controller the layout is rendered by Symfony and only the content at the center would be rendered by the legacy controller wrapped. The first step is to have this controller usable via a forced URL with the legacy controller passed as a parameter.Like the generical Symfony layout is based on a Twig component, this legacy display should also be handled via a Twig component that will look like the generic one a lot except for a few exceptions that we need to anticipate (non-exhaustive list):
AdminController::setMedia(false)
Once the generic controller 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
This controller should be able to display a legacy page ( TBD )
Could be test manually by forcing the URL
Handle legacy page display via the Symfony controller automatically and systematically
UI tests work fine with Symfony layout enabled, and on legacy pages
Test multistore shop list
Test the productcomment in the BO. It should work as ISO
The text was updated successfully, but these errors were encountered: