Closed (outdated)
Project:
Invite
Version:
6.x-2.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
3 Jun 2009 at 10:14 UTC
Updated:
17 May 2020 at 08:50 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Bevan commented#377858: limit as textfield, instead of select list, Drupal 5 is a request for a backport of this. #196250: Invitation limit should not be an input field raises an issue that needs consideration before this can be marked RTBC. The patch is clean and works.
Comment #2
Bevan commentedRerolling for dev branch. Still needs work due to issues raised in #196250: Invitation limit should not be an input field
Comment #3
Bevan commentedComment #4
Bevan commentedComment #5
Bevan commentedThis version of the patch addresses the issue raised in #196250: Invitation limit should not be an input field by validating the user input values for role limits. It needs review and some testing.
Comment #6
sunuser_roles(0) looks scary. Why?
Comment #7
Bevan commentedIt is not using
user_roles(0)to set any values, just to find keys of values in the form submission ($form_state['values']). I copied this iteration technique from:There are 5 other places in
invite.moduleandinvite.installthat already useuser_roles(0)in this way (and one that usesuser_roles(1)).Ideally they would use booleans
FALSEandTRUEinstead of integers, but that is a separate issue.Also, in this case, passing any different parameters such as
user_roles(1)would be an error, since users invited by anonymous users would not gain anonymous users' target role. Though implementing invite.module in this way would probably be an error of it's own (on the part of the configurator)!Comment #8
comrax commentedAre you going to integrate this into 2.x-DEV?
Comment #9
avpadernoI am closing this issue, since it's for a Drupal version no longer supported.