2
There are two solutions (one hack, one module) already out there -- maybe you wanna use them instead of developing a new one.
One is called Registraion Codes (a module + some hack); the other is called Registration Keys (a core hack well integrated into the admin). I wrote a quick (and subjective) comparison between them.
Here's the whole thread.
One is called Registraion Codes (a module + some hack); the other is called Registration Keys (a core hack well integrated into the admin). I wrote a quick (and subjective) comparison between them.
Here's the whole thread.
3
It would be great if that goes to the core. In that case, please also consider adding an option of "Registration Codes required for registration".
4
Quote:
Oops, I used the wrong word. When I said "making it optional" I mean "having the option of using custom codes or system random codes".
Anyway, you got my point. And thanks a lot for this great module.
jegelstaff wrote:
Quote:
tklee wrote:
About the randomly generated password, I'd suggest it being optional. Making it optional allows us to use meaningful keywords to invite people.
...
I've found, among other things, that the registration code box is a required field, so there's no point in having the word 'Optional' beside it. So there's a few polish-related things like that which could go in another release.
Thanks one and all for the interest!
--Julian
Oops, I used the wrong word. When I said "making it optional" I mean "having the option of using custom codes or system random codes".
Anyway, you got my point. And thanks a lot for this great module.
5
I turned PHP debug on and got these:
On the module page (called by a user):
Notice [PHP]: Undefined variable: asl in file modules/reg_codes/index.php line 273
Warning [PHP]: array_reverse(): The argument should be an array in file modules/reg_codes/index.php line 273
Warning [PHP]: Invalid argument supplied for foreach() in file modules/reg_codes/index.php line 274
Notice [PHP]: Undefined variable: tempigroupnames in file modules/reg_codes/index.php line 339
Notice [PHP]: Undefined offset: 0 in file modules/reg_codes/index.php line 339
Notice [PHP]: Undefined variable: thiscode in file modules/reg_codes/index.php line 126
On module admin page:
Notice [PHP]: Undefined variable: grouplist_id in file modules/reg_codes/admin/index.php line 99
Notice [PHP]: Undefined variable: grouplist_name in file modules/reg_codes/admin/index.php line 100
On the module page (called by a user):
Notice [PHP]: Undefined variable: asl in file modules/reg_codes/index.php line 273
Warning [PHP]: array_reverse(): The argument should be an array in file modules/reg_codes/index.php line 273
Warning [PHP]: Invalid argument supplied for foreach() in file modules/reg_codes/index.php line 274
Notice [PHP]: Undefined variable: tempigroupnames in file modules/reg_codes/index.php line 339
Notice [PHP]: Undefined offset: 0 in file modules/reg_codes/index.php line 339
Notice [PHP]: Undefined variable: thiscode in file modules/reg_codes/index.php line 126
On module admin page:
Notice [PHP]: Undefined variable: grouplist_id in file modules/reg_codes/admin/index.php line 99
Notice [PHP]: Undefined variable: grouplist_name in file modules/reg_codes/admin/index.php line 100
6
I'm quoting here so you don't have to look for the original post:
Quote:
I've been using Registartion Key from since it's out and have been very happy with that. When I first saw Registartion Codes module, I felt sorry that information wasn't effectly spreaded and people have done duplicated work.
Trying both, I have some comments:
1. module vs. hack
I agree with Julian that Registration Key is easier to install and upgrade. Two core files to deal with only. On the other hand, being a module and a hack might be somewhat confusing for non-technical admins -- what if they uninstall the module without remembering some core files have been changed? May I suggest wrapping those added codes with a condition statement so if the module is not installed, those codes will get skipped?)
2. invitation from group
Registration Keys is admin-only tool so the webmasters have to do everything; Registration Codes provides the "group invitation by group member" function. That's really cool. I also found automatic expiration very useful.
3. random Codes
About the randomly generated password, I'd suggest it being optional. Keys are all assigned in Registration Keys, but in Registration Codes you only get system generated random codes. Maybe there can be a button or a javascript for the system to generate one if the user chooses to. Making it optional allows us to use meaningful keywords to invite people.
And, salute to both authors.
Quote:
jegelstaff wrote:
RE: Registration Keys...
I'll make a few comments that might help people see where there are some differences. ....
... [omit] ...
It looks to me that the biggest difference between the two modules, from a sys admin perspective, is that Reg Keys is a tightly integrated system module that makes changes to eight core files in a few different places.
Whereas our Registration Codes module is not a system module, and it makes changes to two core files (/register.php and /include/registerform.php).
So if you want something that doesn't alter your XOOPS installation that much, then ours might be the one to go with. If you want something integrated tightly with the core, Reg Keys is probably better.
It seems that Reg Keys was built originally for 2.0.6RC (according to the readme), and at least one of the files it altered is not actually present in 2.0.7 (/registration.php), so that might complicate upgrading or installing it from scratch in 2.0.7 or higher (though I suspect register.php in 2.0.7 is very similar to registration.php in 2.0.6).
Also, our module has a permission system, with which you can control which groups are allowed to create codes for membership in which other groups (so the webmaster doesn't have to do all the code issuing, you could let people in one of your groups issue codes that allowed new users to have membership in only that same group). I'm not sure if Reg Keys has that feature, but it's not mentioned in the readme.
Thanks for reading! Happy XOOPSING,
--Julian
I've been using Registartion Key from since it's out and have been very happy with that. When I first saw Registartion Codes module, I felt sorry that information wasn't effectly spreaded and people have done duplicated work.
Trying both, I have some comments:
1. module vs. hack
I agree with Julian that Registration Key is easier to install and upgrade. Two core files to deal with only. On the other hand, being a module and a hack might be somewhat confusing for non-technical admins -- what if they uninstall the module without remembering some core files have been changed? May I suggest wrapping those added codes with a condition statement so if the module is not installed, those codes will get skipped?)
2. invitation from group
Registration Keys is admin-only tool so the webmasters have to do everything; Registration Codes provides the "group invitation by group member" function. That's really cool. I also found automatic expiration very useful.
3. random Codes
About the randomly generated password, I'd suggest it being optional. Keys are all assigned in Registration Keys, but in Registration Codes you only get system generated random codes. Maybe there can be a button or a javascript for the system to generate one if the user chooses to. Making it optional allows us to use meaningful keywords to invite people.
And, salute to both authors.
7
There seems to be a bug. Here's my temporary fix. In wiwimod/index.php, change
into:
$t_area = new XoopsFormDhtmlTextArea('Content', 'body', '', 37, 35);
into:
$t_area = new XoopsFormDhtmlTextArea('Content', 'body', $body, 37, 35);
8
I think you can't do it in the current offical XOOPS release (2.0.7). You can, however, set a forum readable by individual users (assign one by one), instead of a group.
Note that in module newBB 2.0, a very sophisticated access control scheme is designed. However, it's still in Beta stage:
http://dev.xoops.org/modules/xfmod/project/?newbb
Note that in module newBB 2.0, a very sophisticated access control scheme is designed. However, it's still in Beta stage:
http://dev.xoops.org/modules/xfmod/project/?newbb
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Apr 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|