perfect module for what I'm looking for, client access to a project page.

I was successful in installing and creating a peek page and can view the project node.
I have granted permissions to 'authenticated user' to add, view comments and the specific node fields.
but
Only the node's title and description are visible. I get a Login or register to post comments.

I do have the 'content_access' and CCK's content permissions modules installed. culprits?

Comments

CobraMP’s picture

CobraMP commented

wanted to add a feature request to have the user deleted when the peek is deleted or expired

adixon’s picture

adixon commented

i think what you're asking for is outside the original scope of the module. It's called 'peek' because the user can only look at stuff briefly, it's not going to give them permission to do anything else (e.g. post comments). Other than the initial peek page load, the user has no permissions to do anything. So you'd have to give anonymous commenting ability I believe.

On the other hand, perhaps it makes sense to extend the functionality of the module to do more than just "peeks". Patches welcome ...

Re: deleting users - it creates these users to allow a history for them to accumulate (e.g. if you've got a client that you provide peeks to multiple times).
I believe what you're looking for would be handled better by a more general purpose module that deletes unused/blocked users via a cron.
Check out: http://drupal.org/project/inactive_user

CobraMP’s picture

CobraMP commented

thanks for the reply adixon
my understanding was that peek gave a temporary access as an "authenticated user" therefore any permissions give to an authenticated user should apply to the page being peeked. I think an update would be great, perhaps the ability to grant a specific role would be best beneficial.

another example is I would like to create a menu for the client peeking at their project page with items such as a feedback survey. Of course I could always put the feedback link in the body of the node being viewed.

adixon’s picture

adixon commented
Status: Active » Closed (works as designed)

To extend peek, you probably need to look at the 'peek_show' function to understand how the module works. It's a pretty paranoid module that is really designed for providing a single snapshot view of a node, and nothing else. In it's simplest form, the peeking user gets authenticated as a blocked user (I think .. i might be wrong) that can only see the peek page, which displays the node page (but using a different 'peek' url).

If you want to allow users to do something beyond this, then this might not be the right strategy, since the overhead and complexity of 'proxying' the node page is not something you'd want to extend to say, commenting. For the additional functionality, I think you might want to enable the (temporary?) unblocking of the users and assignment of specific roles that allows this functionality via the usual urls/permissions. But that's really opening up a whole new area that might be better to rethink from the outset.

If you want to keep it simple, i'd recommend that you add all the new functionality for anonymous users, and some form of security by obscurity to keep down the spam.