Skip to content

Prevent email activation warning for running sessions

Alex requested to merge prevent-dashboard-warning into master

What does this MR do?

Workaround for !1334 (merged) before release: users will see a warning on the dashboard if their email address is not activated, which is stores as email_is_activated in the session. All session that are active during the release won't have that flag and will show the warning, too, even if the address is already activated, and will only be correct after a relogin. This is supposed to prevent that.

How confident are you it won't break things if deployed?

Quite sure

Checklist

  • added a test, or explain why one is not needed/possible...
  • no unrelated changes
  • asked someone for a code review
  • set a "for:" label to indicate who will be affected by this change
  • use "state:" labels to track this MR's state until it was beta tested
  • added an entry to CHANGELOG.md
  • add a short text that can be used in the release notes
  • Once your MR has been merged, you are responsible to create a testing issue in Beta Testing Repo:
    • Consider writing a detailed description in German.
    • Describe in a few sentences, what should be tested from a user perspective.
    • Also mention different settings (e.g. different browsers, roles, ...). how this change can be tested.
    • Be aware, that also non technical people should understand.

Merge request reports