We are moving to Git Issues for bug tracking in future releases. During transition, content will be in both tools. If you'd like to file a new bug, please create an issue.

Bug 3470 - "registration notification" emails for both the registree and conference manager would be useful
"registration notification" emails for both the registree and conference mana...
Status: NEW
Product: OCS
Classification: Unclassified
Component: General
To be determined
PC Mac OS X 10.0
: P1 enhancement
Assigned To: PKP Support
Depends on:
  Show dependency treegraph
Reported: 2008-05-07 20:06 PDT by James MacGregor
Modified: 2008-05-21 16:31 PDT (History)
0 users

See Also:
Version Reported In:
Also Affects:


Note You need to log in before you can comment on or make changes to this bug.
Description James MacGregor 2008-05-07 20:06:43 PDT
On self-registration, it would be useful if

a) the registree could opt to have a registration email sent to their email address, with their user and registration information included. 

b) the system sent an email to the conference or registration manager notifying them of a new registration. This would be helpful especially if registrees could include domain/IP addresses, or any other actionable information.
Comment 1 James MacGregor 2008-05-09 10:58:49 PDT
I noticed the following forum post that includes a workaround for part of this: 


The post also references Bug 3234, which should address part of this issue as well. I believe I missed this fix as the user I was registering for the scheduled conference with was already registered with the site, and so would not receive the 'new user registration' email. To clarify: this report is concerned with having

a) a paper trail when a user registers for a scheduled conference, hopefully including payment information. 

b) a notification email (or CC) for the conference manager, so they know a registration has been made and may need to be processed. 
Comment 2 Alec Smecher 2008-05-21 16:31:44 PDT
Deferring, as too many translations have been completed to introduce a new email template. This may be a dupe of bug #3503.