Fix duplicate header in VERIFY_EMAIL flow #46106
Open
+6
−2
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.
When executing the VERIFY_EMAIL action (for example via the admin API), the confirmation page showed "Your account has been updated." twice, once as the page header and once as the body.
The root cause is that
AuthenticationManager.finishedRequiredActions()rendered theACCOUNT_UPDATEDinfo page without setting a messageHeader attribute.The
info.ftltemplate falls back tomessage.summarywhenmessageHeaderis not set, which produced the duplicated message.Change summary:
accountUpdatedTitlewith value "Account Updated".ACCOUNT_UPDATED_TITLE) for the new key.AuthenticationManagerto set themessageHeaderattribute to the message key (ACCOUNT_UPDATED_TITLE) instead of passing a resolved message string. Passing the key lets the template render a distinct header (localized via the message key) and keeps the body message separate.Result:
Notes:
Fix #46105
Before
After