PROD-8414 - Email notifications for secondary replies not working #4616
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ity_comment_posted', 'bb_activity_comment_at_name_send_emails', 12, 3 ); was set to priority 12, causing it to trigger after notifications were already added. This was creating an issue with mentions.
* release: Update: Grunt Update: Grunt string-replace Update: Version name update Added change log grunt PROD-8551 - fix cross-site scripting vulnerability for the forums PROD-8551 - fix cross-site scripting vulnerability PROD-8245 - Fixed - The invites table in the back end of the site does not sort properly PROD-8510 - Fixed - The group type with the setting to hide the groups from the Group Directory hides those groups from the Backend groups directory
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Jira Issue:
https://buddyboss.atlassian.net/browse/PROD-8414
General Note
Keep all conversations related to this PR in the associated Jira issue(s). Do NOT add comment on this PR or edit this PR’s description.
Notes to Developer
Notes to Reviewer