I think it would be nice that Views can provide filtering function based on user profile, for example, administer creates a user profile called "version 6.2 users", then users can create contents and tag proper contents with "version 6.2 users". So when version 6.2 users log in, they can view all version 6.2 related stuff.

Comments

merlinofchaos’s picture

merlinofchaos commented

Actually, this isn't really a filter, it's a relationship. And it's unfortunately difficult to create a relationship of this nature, but it's not totally impossible. But it's also something that I'm not sure core Views would support, as most people would find it very confusing. I'll have to think about it; it might be something better done in a module and added on.

dropall’s picture

dropall commented

I need a profile based filter too.

I suppose that the OP uses taxonomy to tag his content and that's why the relationship is difficult to create.

My situation is different : I use CCK to store the version in the nodes.

I've seen that the current version of views (6.x-2.0-rc1) has no relationship problem with my CCK field.

The current profile filter lists all possible values for the profile field (as defined in the profile settings).

What I need is the same list as the one used in the new field creation.

Instead of "version 6.2 users", "version 5.7 users", .....

I need "Node : nid", ...., "Node : title", ...., "Content: Text: Version (field_version)", ....

rolf van de krol’s picture

rolf van de krol commented
Status: Active » Closed (won't fix)

This issue can be closed because it will most likely never be fixed.

Please reopen if you disagree on this.

--triage-ddd-nl