"Regarding the notification, fortunately we did have the foresight to make this configurable. In the cns language file, change the BIRTHDAY_NOTIFICATION_MAIL language string. Change {4} to {3} as follows:
Code
It's {{{2}}}'s birthday. Come congratulate them on {1}:\n{3}
(3 is passed in as the member profile URL but not used by default; 4 is the birthday topic creation URL)"
This is now deployed for you Rishi :). 50% of this was documentation and the on/off trigger, which you're not using, but you'll see the birthday notifications and links on your panel now send people to e-gifts rather than creating a birthday topic (or people can go to the member profile to start a private topic, for instance).
In the birthday notifications I got today which shows the new directing to e-gift, the linked part of the URL extends only to their first name and doesn't include the last name. Appears the code doesn't like seeing a space there between first and last name :)
just started seeing the following alert on our front page, not sure if it's related to this deployment or the other one (which I haven't explored yet)?
A language entry is missing: _ADDED_COMMENT_ON_UNTYPED
"Regarding the notification, fortunately we did have the foresight to make this configurable. In the cns language file, change the BIRTHDAY_NOTIFICATION_MAIL language string. Change {4} to {3} as follows:
Code
It's {{{2}}}'s birthday. Come congratulate them on {1}:\n{3}
(3 is passed in as the member profile URL but not used by default; 4 is the birthday topic creation URL)"
In the birthday notifications I got today which shows the new directing to e-gift, the linked part of the URL extends only to their first name and doesn't include the last name. Appears the code doesn't like seeing a space there between first and last name :)
A language entry is missing: _ADDED_COMMENT_ON_UNTYPED