Opened 11 years ago

Closed 11 years ago

Last modified 7 years ago

#243 closed improve feature (fixed)

Accepting members with adminaccepter - duplicated profile

Reported by: jeanyves Owned by: jeanyves
Priority: major Milestone: Legacy Resolved
Component: BW Profile Keywords: accepting duplicated profiles


When a member has subscribe several profile with the same email it is detected and each new subscribtion display in the adminaccepter page the previous subscription made.

The problem is that this is not dynamic. The detection is made when the member signup (deos this member have previous profile with the same email, if so record in a text area the list of these previous profile).

The risk is hight, because this information si not sufficient that the accepter accepts the wrong profile.

I think it is needed that for each other profile connected to teh profile display in the adminaccepter page the Status, the name and may be the lastlogin date of the profile is displayed

Also, and easy way to mark a profile as "dupplicated" (a radio box should be added) and the text use for needmore should be able to send additional text to a standard refusal message (to be created)

Change History (8)

comment:1 Changed 11 years ago by jeanyves

  • follow_up changed from none to move to alpha

Still some fix to do :

  • space missing between resultings action
  • duplicated is proposed first, this create confusion
  • new idea : when someone is accepted put a waring if he has duplicated pending or mail to confirm
  • propose a better layout according to member status (italic for mail to confirm, italic red for needmore, red for pending, bigger charset for Active , striked black bold for rejected,stiked gray for takemeout, gray for choiceinactive .. etc). This must be centralized and easy to change (some layouter will work on it some day)

comment:2 Changed 11 years ago by jeanyves

  • follow_up changed from move to alpha to test on alpha
  • Owner set to jeanyves

Space added extra duplicated removed member status displayed with colour code (not yet centralized)

comment:3 Changed 11 years ago by micha

Cant test on alpha due to insufficient rights for my user "lupochen". Anyway I can test it? Anyone else who can test it and mark it production ready?

comment:4 Changed 11 years ago by globetrotter_tt

  • follow_up changed from test on alpha to release

I just tested it on alpha and confirm that the status, name and last login is displayed now.

comment:5 Changed 11 years ago by jeanyves

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

Moved on Live site

comment:6 Changed 11 years ago by philipp

  • follow_up changed from release to none

comment:7 Changed 7 years ago by TimLoal

  • Milestone changed from unassigned to Legacy Resolved

comment:8 Changed 7 years ago by TimLoal

  • Component changed from BW General to BW Profile
Note: See TracTickets for help on using tickets.