This is a snapshot of Indico's old Trac site. Any information contained herein is most probably outdated. Access our new GitHub site here.

Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#576 closed defect (fixed)

Avoid sending 2 emails when there is a conflict during registration

Reported by: jbenito Owned by: lsyroka
Priority: blocker Milestone: v0.97.0
Component: General Version: 0.96.x
Keywords: Cc:

Description

The action to send the email should be atomic, so, if there is a conflict, the email is not resent!

Actually, the email should be sent right after the commit to the DB, because like this we ensure that the info we sent is correct; because the ID of the registrant may change after the conflict.

Change History (5)

comment:1 Changed 5 years ago by jbenito

  • Priority changed from normal to blocker

comment:2 Changed 5 years ago by lsyroka

  • Owner set to lsyroka
  • Status changed from new to assigned

comment:3 Changed 5 years ago by lsyroka

  • Status changed from assigned to in_merge

comment:4 Changed 5 years ago by Leszek Syroka <leszek.marek.syroka@…>

  • Resolution set to fixed
  • Status changed from in_merge to closed

In [bad9731eb0595c9ea0de5b6912eed1440aa5c1cc]:

[FIX] Sending emails after conflict

  • notification emails for new registrants are stored in _emailsToBeSent variable and are sent after commit in the database
  • fix#576

comment:5 Changed 5 years ago by Leszek Syroka <leszek.marek.syroka@…>

In [bad9731eb0595c9ea0de5b6912eed1440aa5c1cc]:

[FIX] Sending emails after conflict

  • notification emails for new registrants are stored in _emailsToBeSent variable and are sent after commit in the database
  • fix#576
Note: See TracTickets for help on using tickets.