Limit length of email subject triggered by event activity when activity is linked to multiple groups
I received a notification of a new event creation; because it was posted to multiple groups, it had a very long subject line:
Stefano Morello created the event The Social Backend: Community-Driven Digital Archives and Exhibits in the groups GC Events and Workshops, DARC (Digital Archive Research Collective), Digital Humanities Initiative, GC Digital Research Institute - January 2019, GC Digital Research Institute January 2018, GC Digital Research Institute – January 2020, Provost’s Digital Innovation Grant Recipients.
Can we limit the number of groups mentioned in the subject line of the email and/or find a way to shorten the title in situations like this?
#2 Updated by Boone Gorges over 1 year ago
- Tracker changed from Bug to Feature
- Subject changed from Limit event titles to Limit length of email subject triggered by event activity when activity is linked to multiple groups
- Status changed from Assigned to Reporter Feedback
- Target version set to 1.17.0
How? Perhaps we can truncate the list after a certain number. If there's one or two groups, we list them. If there's three or more, list the first two, with 'and x more groups'? So: 'Stefano Morello created the event The Social Backend: Community-Driven Digital Archives and Exhibits in the groups GC Events and Workshops, DARC (Digital Archive Research Collective), and 3 other groups'. Or the threshold could be dynamic, depending on the number of characters in the group names: if each name is short, we might show 4 or 5 before truncation; if they're longer, we might show just one.
#4 Updated by Boone Gorges over 1 year ago
Yes, that is a good idea, Ray. The tricky thing in that case, though, is that the text of the activity action printed in the email body will be different from what's used for the email notification. So we'd need to intercept the email at the level of BPGES rather than simply changing the text of the activity item generated by bp-event-organiser. This is a bit harder technically, but I think you're probably right that it's the best solution.
#6 Updated by Raymond Hoh over 1 year ago
- Status changed from Reporter Feedback to Staged for Production Release
- Assignee changed from Boone Gorges to Raymond Hoh
- Target version changed from 1.17.0 to 1.16.8
This ticket intersected with #12505, so was able to fix this at the same time!