Incubator » CB GroupJive

All core GJ notification types now handled. They are as follows:

user_join
user_cancel
user_approve
user_accepted
user_rejected
user_leave
group_approved
group_pending
user_invite
invite_accept
invite_reject
group_message

They're considered subtypes and used as follows.

groupjive.group.GROUP_ID.SUBTYPE

Example as follows.

groupjive.group.4.invite_accept

In this case the owner should be the user accepting the invite and the user (recipient) should be the user who sent the invite as it's notifying them that their invite was accepted.

Additional GJ Event notifications as follows.

event_approve
event_approved
event_edit
event_attend
event_unattend
event_message
event_new (same as no subtype)

Example as follows.

groupjive.group.4.event.5.event_attend

In this case the owner of the notification is attending the specified event in the asset.

Additionally the below GJ Event activity subtype is now parsed.

event_attend

This would allow an activity entry to state the owner of the activity is attending the specified event in the asset. Usage is same as above for notifications.

Additional GJ File notifications as follows.

file_approve
file_approved
file_new (same as no subtype)

Additional GJ Photo notifications as follows.

photo_approve
photo_approved
photo_new (same as no subtype)

Additional GJ Video notifications as follows.

video_approve
video_approved
video_new (same as no subtype)

Additional GJ Wall notifications as follows.

wall_approve
wall_approved
wall_reply
wall_new (same as no subtype)