- Issue created by @abu3antar
- ๐ฎ๐ณIndia chetan 11
chetan 11 โ made their first commit to this issueโs fork.
- Status changed to Needs review
about 1 year ago 12:59pm 22 November 2023 - ๐ฎ๐ณIndia chetan 11
Hi,
I have fixed the above error on my local setup, please check the attached MR once.
Thanks. - Status changed to Needs work
8 months ago 6:36pm 7 May 2024 - ๐ธ๐ณSenegal diaodiallo
Hi Chetan, thanks for working on this.
After quick review of this I think we need not just to return a default name but also do more i.e about the frequency around that post. arora.shivani โ made their first commit to this issueโs fork.
- Status changed to Needs review
8 months ago 9:37am 8 May 2024 Hello,
I have created a patch for it , Please review. I am not able to push the code from my new branch due to restricted access rights.
Thank you!- Status changed to Needs work
8 months ago 10:41am 8 May 2024 - ๐ธ๐ณSenegal diaodiallo
I actually think the work around this should focus on the deletion process.
#1 Someone remove a post.
#2 A hook (something like hook_ENTITY_TYPE_delete()) check if this node id has a forum_notification_frequency (this nid means the entity_id of the frequency)
#3 If That forum_notification_frequency exists it removes it.Here is the Entity definition itself
Here is how to get notification by id
So should implement the same thing to get notification by subscribed entity id (entity_id) in the ForumNotificationsSubscriptionService class.
After finding it we should delete it so we will no longer fall on it when looping frequencies in the user_form.
Please let me know if someone want to work on this or if there is any need for clarification.