|
|
2 年前 | |
|---|---|---|
| .. | ||
| Controller/Adminhtml/Notification | 2 年前 | |
| Model | 2 年前 | |
| Test | 2 年前 | |
| Ui | 2 年前 | |
| etc | 2 年前 | |
| i18n | 2 年前 | |
| view/adminhtml | 2 年前 | |
| LICENSE.txt | 2 年前 | |
| LICENSE_AFL.txt | 2 年前 | |
| README.md | 2 年前 | |
| composer.json | 2 年前 | |
| registration.php | 2 年前 | |
This module serves to provide a notification delivery platform for displaying new features of a Magento installation or upgrade as well as any other required release notifications.
The Magento_ReleaseNotification module creates the release_notification_viewer_log table in the database.
All database schema changes made by this module are rolled back when the module gets disabled and setup:upgrade command is run.
For information about a module installation in Magento 2, see Enable or disable modules.
Extension developers can interact with the Magento_ReleaseNotification module. For more information about the Magento extension mechanism, see Magento plug-ins.
The Magento dependency injection mechanism enables you to override the functionality of the Magento_ReleaseNotification module.
You can extend release notification updates using the configuration files located in the view/adminhtml/ui_component directory:
release_notificationFor information about a UI component in Magento 2, see Overview of UI components.
Release notification content is maintained by Magento for each Magento version, edition, and locale. To retrieve the content, a response is returned from a request with the following parameters:
The module will make three attempts to retrieve content for the parameters in the order listed:
If there is no content to be retrieved after these requests, the release notification modal will not be displayed to the admin user.
The modal system in the ReleaseNotification module can have up to four modal pages. The admin user can navigate between pages using the “< Prev” and “Next >” buttons at the bottom of the modal. The last modal page will have a “Done” button that will close the modal and record that the admin user has seen the notification.
Each modal page can have the following optional content:
The Sub Heading section is ideally used on the first modal page as a way to describe one to three highlighted features that will be presented in greater detail on the following modal pages. It is recommended to use the Main Content -> Text Body and Bullet Point lists as the paragraph and list content displayed on a highlighted feature’s detail modal page.
A clickable link to internal or external content in any text field will be created by using the following format and opened in a new browser tab. Providing the URL for the link followed by the text to be displayed for that link in brackets will cause a clickable link to be created. The text between the brackets [text] will be the text that the clickable link shows.
The text: https://devdocs.magento.com/ [Magento DevDocs]. will appear as Magento DevDocs.