Yes, unless you explicitly mark them as unread. Then they stick around.Do reaction alerts automatically mark as read when you view them on the menu?
Yes, unless you explicitly mark them as unread. Then they stick around.Do reaction alerts automatically mark as read when you view them on the menu?
Fantastic, thanks!Yes, unless you explicitly mark them as unread. Then they stick around.
- Make global "mark read" work without a overlay or redirect to a new page, and reload alerts on the existing page when invoked
- Handle alerts unviewed/unread being out of sync so trigger summarization
- For reaction summary alerts
- Ensure reactions have stable sorting (new summarizes only)
- On generating summary alerts, ensure they are treated as just-read correctly in the UI.
- On viewing details, Fix the new alert star was being put under the avatar incorrectly...
Clicking on "mark read" redirects to
- Make global "mark read" work without a overlay or redirect to a new page, and reload alerts on the existing page when invoked
Read the rest of this update entry...
/account/alerts/mark-read
again (at least from the alerts menu). Doesn't seem like this was intended The link in the footer of the alerts dropdown.Which 'mark read'?
2.1.12What version of XenForo?
Yep, including clearing the cache.Have you reloaded the page after the add-on finished installing?
- Adjust locking ordering in markUserAlertsRead to hopefully be less deadlock prone
- Add sanity checking to unread alerts page to automatically rebuild alert counts on no unread alerts being seen
- Adjust lock ordering to reduce/prevent deadlocks between the mark read/unread feature and inserting alerts
- Note; this affects stock alerts as well.
- Fix that mark read/unread would silently fail if an alert went away
- Fix bulk alert toggle could be inconsistent compared to the individual alert toggler with how it manipulates is-read/is-recently-read/is-unread classes
- Add public account/alert route, allowing nicer URLs for alert specific actions
- Fix...
- Fix that mark read/unread would remove the checkbox on the alerts page
- Push fauxBlockLink to be just around the per-template render to not overlap the minor info row
I would prefer to get it right the first timeGreat work @Xon, thanks for the speedy updates on this!
This sort of feature is what I'ld put into Report Centre Essentials or Moderator Essentials for this sort of moderation automationWould you consider a staff CC function for "reason" alerts?
So for example. An admin deletes a thread, and fills in the reason "Promotion in the wrong area."
The moderators gets the same alert the user did with adjusted language letting know the admin that deleted it and the reason.
This is good to keep mods on their toes and looking out for certain violations. This would be for edits, deletes, and all the "reason" actions.
The setting could be in the user group or in the mod and admin staff settings. Something like:
Receive CC of actions sent with a reason by administrators Y/N
Receive CC of actions sent with a reason by moderators Y/N
OR it could be a CC tick box when actually sending.
This way you control if mods get it from admins, or from other mods, or admin to admin, etc. Great for training mods or just giving staff a heads up to current actions.
Thanks!
Check you don't have an outdated template (and the latest version), v2.8.13 definitely has the correct phrases there;
- Fix that alerts css would be injected after extra.less, which made styling difficult
- Rework alert pruning to better scale for large & busy forums
We use essential cookies to make this site work, and optional cookies to enhance your experience.