Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
erp5 erp5
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 141
    • Merge requests 141
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • erp5erp5
  • Merge requests
  • !492

Merged
Created Nov 13, 2017 by Jérome Perrin@jeromeOwner

Normalize notification message references

  • Overview 2
  • Commits 4
  • Changes 12

We realized that the references of notification messages used in credential request management had a typo (crendential vs credential) and that the message used for a new credential request was not using the same credential_request prefix as others.

This MR changes the messages as follow:

Wrong Reference Correct Reference
erp5-subscription.notification credential_request-subscription
crendential_request-confirmation-without-password credential_request-confirmation-without-password
crendential_request-confirmation-with-password credential_request-confirmation-with-password
crendential_request-confirmation-without-password credential_request-confirmation-without-password
crendential_recovery-reset-link credential_recover-reset-link
crendential_recovery-username credential_recovery-username

This is an incompatible change that can affect projects that have defined some custom notification messages without explicitly setting the references on the system preferences (ie. getting the default value from the property definition). I found one project using custom notification messages, but preference was defined. Other projects I checked did not override these notification messages.

In our projects, we mostly use messages for credential requests, but the reference for the notification message is usually defined as a property of the web section.

So I'm confident this should not affect projects and we can proceed with this clean up without causing too much troubles. To check if you need to adjust notification messages, check if you have customized notification message with reference Wrong Reference.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: fix/notification_message_references
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7