Function _invite_set_timestamp() uses the reg_code as e unique key to update the invite table. The reg_code is not garantueed te be unique though.

CommentFileSizeAuthor
#1 invite_unique_reg_code.patch879 bytespjdevries

Comments

pjdevries’s picture

pjdevries commented
Title: Using reg_code as unique key » Fixed
StatusFileSize
new invite_unique_reg_code.patch879 bytes

I implemented a simple solution that solves the problem (see attached patch). Rather brute force but it seems to work. The cvs diff left me with a patch containing carriage returns but I took the liberty to remove them from the patch.

pjdevries’s picture

pjdevries commented
Title: Fixed » Using reg_code as unique key

Accidently changed the title into something rather unrecognizable, so need to change it back:)

ajk’s picture

ajk commented
Status: Active » Closed (duplicate)

see http://drupal.org/node/85708