Hi,

I'd like to hide some fields from non-registrered users, showing them only to users who are logged in. I've read this topic in the forum which suggests that this is not possible; is that correct? Hiding them with css, as suggested in that topic, is not an option for me as the data will still be in the html and these fields will contain sensitive information like names and addresses. I do not want a clever guy to find this out.

I was thinking of an approach that might solve this problem, hope you can give me feedback. We have planned three types of views for the items:
1. a view showing all categories, each with the titles of 5 most recent items in that categorie;
2. a list of all items per category (with pagination);
3. the detail view of an item

If I could make the first two views public and the 3rd only accesible for registered users, then my problem would be solved. I'd just have to make sure that in the first two views there are no fields that should not be visisble publicly.

Would this be possible? Would it make sense?


Kind regards, Frits


Edit: Just for the record: there will also be a view for submitting items in the front end. As far as I can see, limiting access to this view to registered users is no problem.

Hello Frits,

You can directly render extrafields to registered users only but they will still be present in JSON and RSS feeds.
A scrapper could see all these data and you really do not want this.

I think a custom K2 plugin should be used for handling these sensitive data.

Hi,

When saying "custom" you mean that there is not such a plugin available at the moment and it should be developed?


Kind regards, Frits

A similar plugin might be present in the JED or getk2.org/extend . It is worth to take a look, but most likely you might need a new extension.

Ok, I understand.

And how about my idea for a solution as described in my first post: restricting access for non-registered to the list views, leaving the detail view for registered users. Would there be a way to accomplish this?


Frits

It can be done via template overrides.
You will have to modify your JSON feeds not to show your fulltext though.