By El Bandito on

Hi

I have a bad feeling I know the answer to this one from other posts, but I'll try anyway. I am creating a site where authenticated users will be able to create a CCK custom content type. However some of the fields are not for public consumption, and are only of interest to the authenticated users i.e. anonymous users must NEVER see these fields whether the node is displayed directly OR via a View or somesuch.

I have read that the Content Permissions module that ships with CCK somehow doesn't actually stop Google seeing the full node ? Is this the case ?

Can anyone suggest an alternative ? Am I going to have to hive off the private data into a separate node ?

Thanks

Dave

⋅ Categories: Drupal 6.x

Comments

WorldFallz’s picture

WorldFallz commented

I've not heard anything about google seeing private fields. do you have a link? google crawls the site as an anonymous user-- if anonymous users can't see something google shouldn't either. Maybe check with the folks on http://drupal.org/irc...

El Bandito’s picture

El Bandito commented

Thanks for your response.

The reason I am presuming this is the following paragraph taken from http://drupal.org/project/cck_field_perms :

"CCK Field Permissions does not prevent Drupal's search engine from indexing content that a user might not have access to. This is due to how the search engine interfaces with CCK nodes. Idealy this could be fixed by adding permissions into the core of CCK, however I'm not sure that there is significant interest in that."

AAaaaaah, just re-read it. Says Drupal's search engine NOT Google. So presumably as long as Search is disabled all would be OK.

I've also found this module http://drupal.org/project/cck_private_fields which looks ideal for my use case.

Cheers