Bug #867

User with 0 invitations receives strange error messages when inviting new users

Added by Leonidas Poulopoulos almost 11 years ago. Updated almost 11 years ago.

Status:Closed Start date:07/19/2011
Priority:High Due date:
Assignee:Giorgos Gousios % Done:

0%

Category:deployment Spent time: -
Target version:v0.5.3.1

Description

When a user has no invitations and proceeds to inviting someone, then an informational message shows up indicating that: "Invitation to XXXX YYYY <> not sent. Reason: User with email already invited". What is strange is that the error message states that "User with email already invited". This message comes up regardless of the user that is to be invited.
When the user with 0 invitations, tries to invite the same person twice, then (having received the pre-mentioned message on the first attempt) the error message changes to "Invitation to XXXX YYYY <> not sent. Reason: User invitation limit (0) exhausted"

Associated revisions

Revision d53bbf68
Added by Giorgos Gousios almost 11 years ago

Be a bit more careful when initializing exceptions

The problem seems to be that the code incorectly used a class variable which was
initialized once and exception messages where appended to it by both TooManyInvitations
and AlreadyInvited exception types, hence the fuzzy error reporting.
Fixed by using instance variables.

Refs: #867

Revision 65fb614f
Added by Giorgos Gousios almost 11 years ago

Be a bit more careful when initializing exceptions

The problem seems to be that the code incorectly used a class variable which was
initialized once and exception messages where appended to it by both TooManyInvitations
and AlreadyInvited exception types, hence the fuzzy error reporting.
Fixed by using instance variables.

Refs: #867

History

#1 Updated by Vangelis Koukis almost 11 years ago

  • Category set to deployment
  • Status changed from New to Assigned
  • Assignee set to Giorgos Gousios
  • Priority changed from Medium to High
  • Target version set to v0.5.3.1

#2 Updated by Vangelis Koukis almost 11 years ago

  • Status changed from Assigned to Closed

Merged, closing.

Also available in: Atom PDF