I'm doing some testing on content_profile now, and wanted to throw this idea out there.

Feel free to shoot it down in glorious flames!

Here is the use case: a site where anonymous users can't see user profiles.

Problem: with content_profile, users are nodes, and if anonymous users can search the site, they can see user profiles.

Possible solution (and this is where feedback is requested): create an admin option on nodes that are used as profiles to have all nodes functioning as profiles not be indexed for anon users.

Another method (and probably a better method) would be to have profile nodes leverage the same access control mechanism as user profiles; ie, if a role has rights to see user profiles, it has rights to see nodes used as profiles via content profile.

Just thinking out loud here, but wanted to get an issue in to get feedback from other folks on this.

Comments

fago’s picture

fago
Primary language German
Location Vienna
commented

an interesting idea.. :) But you would need a node access module to implement it, perhaps this could be another nice extension module.

Personally I'm using content access to configure that - however the 6.x port is not yet finished. I'm working on it, puh.

bonobo’s picture

bonobo commented

Yeah -- content access could do it. Workflow access would also work for this, now that I think about it.

I go back and forth about wanting to have a separate access control mechanism for this, or whether the access control mechanism should be keyed off the ability to access user profiles.

bonobo’s picture

bonobo commented
Status: Active » Postponed

Setting to postponed -- this is not a big deal, and there are ways of addressing this.