Add dashexample module for the new Symfony dashboard hooks#254
Open
mattgoud wants to merge 1 commit into
Open
Conversation
Registers displayAdminDashboardZoneOne, displayAdminDashboardZoneTwo and displayAdminDashboardToolbar, rendering content through module Twig templates (no Smarty, no HelperForm, no Db::getInstance()) and loading its own assets from its hook output (no actionAdminControllerSetMedia / class-name detection). Serves as living documentation of the new integration contract and as a validation vehicle for the migrated dashboard (PrestaShop/PrestaShop#41968).
This was referenced Jul 17, 2026
Migrate Dashboard to Symfony behind a beta feature flag (initialization)
PrestaShop/PrestaShop#42077
Open
Draft
jolelievre
reviewed
Jul 23, 2026
| return parent::install() | ||
| && $this->registerHook([ | ||
| 'displayAdminDashboardZoneOne', | ||
| 'displayAdminDashboardZoneTwo', |
Contributor
There was a problem hiding this comment.
Suggested change
| 'displayAdminDashboardZoneTwo', | |
| 'displayAdminDashboardZoneTwo', | |
| 'displayAdminDashboardZoneThree', |
An exemple with zone 3 would be nice
|
|
||
| {% trans_default_domain 'Module.Dashexample.Admin' %} | ||
|
|
||
| {# The module loads its own assets from its hook output — no actionAdminControllerSetMedia, |
Contributor
There was a problem hiding this comment.
It's interesting to have this alternative as an example, but I don't understand why we hunt the actionAdminControllerSetMedia so badly in this migration. This hook is used widely on every page for any module integration, and it's a common usage
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds a new example module,
dashexample, that demonstrates how a module integrates with the migrated (Symfony) Back Office Dashboard through its new dedicated hook family.It is both living documentation of the integration contract and a validation vehicle for the dashboard migration (core issue PrestaShop/PrestaShop#41968).
What it demonstrates
displayAdminDashboardZoneOne,displayAdminDashboardZoneTwo,displayAdminDashboardToolbar.HelperForm, noDb::getInstance().date_from/date_to).actionAdminControllerSetMedia, noget_class($this->context->controller)detection.The
README.mdexplains the legacy-vs-Symfony hook families and how a single module can register on both to support multiple PrestaShop versions.Requirements
dashboardfeature flag enabled (Advanced Parameters > New & Experimental Features).How to test
dashboardfeature flag.php bin/console prestashop:module install dashexample.Related