I have no idea which project this should go to so sorry if I have gotten it wrong. Also, although I have these listed as three issues, I wonder if they are not all related? Tell me and I will re-post, separate, whatever. As for the priority, it feels critical to me because i have a social network site and if messages aren't going out correctly, this is a big deal.

I am running D6.14, messaging 2.2, notifications 2.2, OG 2.0 - so I am supposedly current. I have two users set up to get notification messages for node create, update, and comment. User1 uses outlook and authenticated user uses yahoo. There are images attached so you can see what I am talking about below.

first issue: incorrect template - The user1 gets create, update, and comment messages/notifications from OG okay. The authenticated user gets the same. The attached screen shots show how the authenticated user gets the correct message template for the OG messages where as user1 does not.

second issue: missing message notifs - both are set up to receive notifs when a regular content type is created, updated, commented. User 1 gets the notifications (sometimes late) but the authenticated does not get any. If this because the authenticated user only gets OG templates and not the others? User 1 gets all his messages via the default notification templates so not sure what's up.

third issue: token value incorrectly shown - I have seen someone talk about this but now I can't find the post. A notification message for a node create does not show the alias url (it shows node/#) but for an update message does show the alias. When the OG notifications template gets triggered for the authenticated user (see yahoo messages), the new post shows an alias url correctly. So it seems like there is something wrong with the "notifications for node creation" and how it interprets the url token.

Are these related? Did I put these in the right project queue?

help!
thanks

Comments

jose reyero’s picture

I think most of these are og_notifications issues. (Organic Groups)

Please do some research on the open issues there (I think there are duplicates) before re-posting, one issue at a time.