To start when a post gets deleted ... have a look into OssnWall->deletePost()

You find a callback being triggered like

ossn_trigger_callback('post', 'delete', $post);

Register that callback in your component like

ossn_register_callback('post', 'delete', 'removeMentionNotification');

removeMentionNotification(....) {
// remove accompanying notification record of type 'mention:post:created'
}

The other parts are basically similar, find the triggers in OssnUsers->deleteUser() and OssnComments->deleteComment()

Z,

Can you help me understand point A better. Are you saying I need to implement a new hook on a delete comment or delete post that will delete the notification? Im just trying to understand. This one is new to me. Obviously from a programming and flow perspective I get the importance, just need to understand the OSSN implementation better because Im not sure if this would be like this

add a hook to the delete action >> check to see if notification is pending on deleted item >> delete notification if item is deleted >> else display the notification

or this

upon clicking the notification icon >> check to see if notification is pending on deleted item >> delete notification if item is deleted >> else display the notification

or

something else

Thanks!

Hey no worries Z-Man,

I appreciate all the help I can get. I will be happy to implement your change idea. I will delete v1.1 so no one grabs it in the mean time but I will try to get v1.2 with that change uploaded tonight. Thanks again man, I really appreciate the helpfulness.

Bryce

Great idea and a good start, Bryce!
But I'm still not really happy with version 1.1

A) Whenever you create new database records in general - asure they will be deleted if necessary. In this case:
1. if the posting / comment has been deleted by the originator
2. if the originator has been deleted / has left the community

Otherwise you'll end up with orphan records and notifications pointing into the blue here.

B) com_notificationHandler() is a fair solution for communities with a handful of users, yes, but fetching a complete userbase with thousends of members will make your function a real monster, eating up memory and maybe even result in timeouts. Thus, instead of fetching the complete list and do a comparison whether the mentioned user may be part of it I'd recommend to make use of OssnUsers->searchUsers() instead. This way you need only one query and either you get something back or not.

V1.1 has been uploaded with Arsalans suggestions addressed

Excellent, thank you, I will add that for v1.1 tonight

You should be able to add icon in com_mention_notifier_view_notification or once you updated the type, the notification item should get a html class , you can view source code of browser and see which class is assigned to li, then using css you can use fontawesome (this is second approach)

Yep thats the one. I was wondering if it is easy to wire up a new icon type like for my mention:component:post type for example

You mean the icon display in notification view box?

Good point Arsalan, I guess I didnt consider that could have ramifications. Im at work now and will adjust it after I get home so Im going to delete the upload so no one else grabs it until v1.1 is done. BTW, any advice on how I can get a little font awesome icon to show for my type similar to how

post:created

does in the notification template?

Thanks for the input!