Well this is interesting..! JammyDodger’s reply led me to more experiments.
Renaming the automatic groups via the site text setting led to some confusion when spaces were involved, because spaces prevent them being used as handles. If the current derived handle isn’t overridden by the site text setting because of spaces, it stays as it was. I discovered this when I briefly got a no-spaces group title stuck as the handle.
Awareness of the impact of spaces and use of the Sidekiq job EnsureDbConsistency cleared things up.
I’ll amend my suggestion in the original post re. displaying proper names in the inbox, as that wouldn’t jive with the use of @-mentions, which require the handle.
Detailed testing steps
-
Starting with my situation above, I confirmed that the Sideqik job had run, and ran it again anyway. Indeed it did not pick up the name changes for the inbox – because of the spaces, as you explained.
-
Changed the site text for TL2 from “Trust Level 2” to “Sophomores” and ran the Sideqik job:
The name change now propagated, as both the group title and the inbox handle – because no spaces:
- Changed the site text name back to “Trust Level 2” and ran the Sidekiq job. The handle assigned in the previous operation is now stuck there – apparently because the spaces in that site text title don’t make for a valid handle:
- Reverted the site text to default “trust_level_2” and did not run the Sidekiq job. This updated the title but not the handle:
- Ran the Sidekiq job, which cleared the edited handle, resetting it to the default in the inbox:
