Additional information about the invited

That makes sense, and since the invited usually gets a user account generated, perhaps that feature could be connected to any profile fields.

But give me more of a spec. here - who and how would the name get added, and how would it be used?

It's also helpful if you can provide more context of your proposal, tell me the whole story.

Well, in my case I would like to enable for my users to invite different viewers from different company's, so names of the invited, and names of their company's would have to be a minimum of additional info. One extra field for a note would also come in handy.

1. I guess this info could be filled in where the usual info gets added ['node/%node/peek']. But the way that you have solved it today with ['node/%node/peek'], the GUI is clean and self explanatory, so I suppose you shouldn't mess that up.

2. But if one, later on, would like to add even more info fields, maybe a special page for this administrative task would be better suited, e.g. ['peek/%user/invitees']. Each user would then have a list with invitees that could be accessed from ['node/%node/peek'].

Hope this makes sense as well, and that it's enough info for you to go on, as a starter anyway!

//Patrik

Hi!
Can I help you with some additional information about my request?

//Patrik

Hi Patrik:

okay, i've had more of a look at this [apologies for the delay - I had to familiarize myself with the Drupal 6 upgrade, or at least thought I did].

so the short answer is - i'm not convinced that this is the right place to put this feature.
Like any good Drupal citizen, peek doesn't try to overlap or replace existing features of Drupal, but cooperates. So instead of managing 'peek users' by itself, 'peek users' are always Drupal users, so any additional information about them should be managed with the existing Drupal tool [usually the profile module, but you can choose].

to consider your specific example - what you would do is import those users before 'peeking' them, using the excellent 'user import' module, but don't notify them, and set their status to 'blocked' [you can add them a role to help bulk management]. Then, new peeks make use of these users, and you can make use of all your normal user management tools.

the key piece of information you might want to understand is: when a peek is generated for a user, Drupal starts by looking up that user (remember that Drupal users are uniquely keyed by their email address), and creates one if it doesn't exist [check that code - it creates it minimally, and blocked].

[functionality already contained in other Drupal modules]

Hi, adixon!
Thanks for taking your time with this, and your serious approach. I understand what you mean and you are absolutely right about overlapping features of Drupal. Thanks for the lesson about how to solve my problem, I will surely use this approach.

Best Regards
Patrik