I do not understand how to get the group_id and group_title from the Invitation Key generator to:

1. The Invitation Template

OR more importantly,

2. the Register Form

To test this I used the same code as IRA42, and all I get on the Invitation is Group ID = 1 and Group Title = Superadmin, in other words, the selection in the key generator:

does not seem to affect anything in the invitation template.

And the documentation does not say clearly how the group_id and group_title is supposed to control the group to which the users is registered when it comes to the actual registration process

Can anyone help please?

This is old, but I just came across looking for something else.

I believe that you don’t pass the member group id directly, you just pass the invitation key like this:

That said, this isn’t stated clearly in the docs and I’m having trouble getting this to work properly myself.

Also, for the record, the url for the registration form needs to have “key” in the segment before the actual key - a bit like the tag module.

Christy,

I’ve managed to get this to work. I’ve also looked at your template code and managed to get it to work. I’m not sure if you’ve done anything since this post as to experimenting though

You’re basically correct… what you need is a seperate template set up for Key Registrations. This is the template you would point users to.
An example of what the beginning of a loop for that Register template would look like is:

I’ve added:

require_key="yes”
key_email_match="yes”

Within the form template, as you noted, you’ll want to add this to the loop:

In your Key Notification template, make sure you link to it like such:

OR

etc

The path of course, can be whatever you wish

I’ll clarify the Docs

That was simple!  I thought those were optional parameters.  Thanks Kelsey.

-C

ruraldreams - 05 May 2008 11:17 AM

I thought those were optional parameters.

Haha, well, they are actually

But I’m assuming that in most cases, if you’re using a Key Invite, you want them to use that key

An example of why require_key might be optional. 

Say my regular registration form is at site/register, and I want to give a key url of site/register/key/{key}
Regular visitors are in the “members” user group and invited members are in the “special members” user group or the “extra-special members” group. Then one wouldn’t have to have multiple registration forms.

But I’ll take it any way it works

ruraldreams - 05 May 2008 01:31 PM

An example of why require_key might be optional. 

Say my regular registration form is at site/register, and I want to give a key url of site/register/key/{key}
Regular visitors are in the “members” user group and invited members are in the “special members” user group or the “extra-special members” group. Then one wouldn’t have to have multiple registration forms.

But I’ll take it any way it works

Yep, definately reasons for not wanting it as well
Though, your explaination is definately a really good example of a usage for it