views_profile implementation

Nice! I will test ASAP.

It'd be great if merlinofchaos, the Views author, and others with knowledge could help out from that side. I think a lot of people would be interested in this.

The next question is how this relates to the profile as CCK type activity (http://drupal.org/node/68360). Thoughts?

--D
http://www.wovenlabs.com

This is really great! I was looking for exactly this type of user display capability. Here are a few issues I noticed and a few questions:

issues
- I can't get all users with profiles to show up. It only lists 3 users, even though I have 10 on a test site? I'm not even sure why the 3 users are showing up vs the others? There isn't anything unique about these 3 users. I've filtered by "Profile: Distinct", but even when this isn't filtered, I only get 3 users.

questions
- is there a way to link to a user profile from one of the profile fields, like how "node:Title" works?
- is it possible to bring in user e-mail addresses?
- will it be possible to sort by profile fields?
- how do you deal with checkbox display?

Thanks and great work so far.

I'm following this but I have not had time to analyze this.

1) It is likely to be accepted in the end, so without a doubt, *continue working on this*, please! I am ecstatic to see this functionality made available.

2) Patching views_user.inc is perfectly acceptable for fields that are there, and that can be included in this patch or posted as a separate patch depending on which is easier.

3) There is a profile node module I think, and a bio module as well. Either of those might adequately serve as an 'anchor' node for doing user lists. It'd be worth looking at them, because I'd be more than happy to recommend one. All that really matters is that there is an anchor.

4) When I skimmed through the code, I didn't see anything that invalidates the views cache when profile fields are changed. This is likely to be necessary. TO see what I mean, get everything set up the way you want. Then go add a profile field. Then immediately go to views admin; if I'm right, the new field won't show up in the views data until something invalidates the views cache. I think profile has a hook for this but I don't remember for sure.

Thanks for following, merlinofchaos.

I too can only gets users who have actually posted a piece of content to show. Is this an inherent limitation w/ the views.module?

I should be able to decide whether to include blocked users or just show active users, and this should be possible via a User: Is Active filter or something like that. Would this be added to views_user.inc?

I'll keep playing.

perhaps you can use the "usernode" module for this, which I'm currently developing
it automatically creates a node for each user in the system.

it's basically working, however there are still some ways to delete the nodes, which i want to prevent. I'm going to add views support too, so that it's possible to list the users's data (mail, registration time, ..)

i know that there is already a module called usernodes, however the name fits very well to my module, so I decided to use 'usernode' nevertheless.

@access: you can set the default optionf of "published" to false for the usernode content type, the usernode module will respect this setting. further I've just comitted an update, which adds a permission "edit own usernode".

@views integration:
yes that's what I'm thinking off. however, currently I'm not using the node author field for the uid entry, (but it's also filled with the same uid), but i store the uid in an extra table.
So I'll add views integration which uses the extra user id - so the fields will show up proper as user fields and not as author information..

Because Views links the user object to the node, having an integration that does NOT use $user->uid == $node->uid will be a weaker integration (from Views' perspective) than another path.

If you're filling the author with that data anyway, I would highly recommend just telling Views that's the linkage. For one, it'll save a join, and for 2, anything which Views links to the user object via node author will work; otherwise, it'll be *very* confusing for people.

i just replyed here, as I don't want to overtake this issue with my stuff.. ;)
you can comment using your drupal id

I'm back at this, trying the latest .inc Mathias provided.

I don't see a filter for user status (active/blocked).

Do we have a proposed solution for the issue where only users who have contributed nodes are shown? This would be nearly there for me if I could just get all users to show. I think this has to do with Earl's "anchor" talk -- he recommended other modules to look at.

Eager to try an updated version.

I've just added some views integration to my usernode module.
(I reused code of the views_user implementation and your patch - thanks)

now you can use the module to provide user listings itself.

any real world examples?
thanks

fago, I can't find your usernode module that's mentioned. Do you mean the usernodes.module (http://drupal.org/node/50850) or your node profile project (http://drupal.org/project/nodeprofile)? Ready to try this right now.

Sorry, usernode.module was in your Node Profile package. I installed it, none of the other modules.

First off, it conflicted w/ views_profile.inc in trying to redeclare views_handler_field_email(), so I had to disable views_profile.inc. That means that I now can't use any of the custom profile fields in my view (unless another module of yours handles this?).

Second, while I now can see all users in the list, many of them show over and over, some five times, even though the Node: Distinct filter is set.

Also, I'd like to use a placeholder image if the user doesn't have a user photo for layout consistency, but that's getting way ahead of where I'm at.

I'm, trying to show a nicely-formatted list of users, with select information from their profile. Is this a really complex thing? :( Anyone interested in helping me if I put a modest bounty on it?

--D

yeah, as I wrote, I reused code from this patch - every information which belongs to the user not to his profile is already offered by the usernode module - and yeah this patch needs to be updated to work with the usernode module again - just remove the information which usernode already provides.

the placeholder image should be possible to achieve by theming a view I think.

this thread is about the views_profile.inc - please use the nodeprofile issue queue for further questions, ideas on my project (or usernode) - you 're welcome.. :)

@multiple nodes: can you provide more details? a view export would be fine.. please open an issue for this..

I'm, trying to show a nicely-formatted list of users, with select information from their profile. Is this a really complex thing? :(
that's what I'm working on and it's already possible, however not by using the core profile.module....

please excuse me as i haven't read every post here ... i think profile.module is a bit discredited at this point among drupal shows making real sites. we all use hook_user, just like profile.module. so a views_profile module that only pulls from profile.module tables is of some use, but not that much. i actually prefer the user => node mapping approach. i haven't tried fago's module, but conceptually it works for me.

hm sry, I don't wanted to tell you how to do your patch. however I've jused the email handler function from your patch, and if one uses usernode module and your patch, you 've to remove the function from one... ;)

So if your patch gets committed I remove the handler from usernode and there is no problem. for now, the handler isn't in views and I need to provide it myself so that the usernode views integration works.

first I thought the incompatiblity (I never tried your patch!) came through duplicate field definitions (email, status), but I think that's not the case. it should be just the handler..

I've changed the function names of the usernode handlers, so there shouldn't be any conflicts any more.

Hi. I had actually removed the duplicate declaration and it worked fine. The latest Node Profile stuff from fago fixes the issue, anyways.

I actually successfully have a view that pulls some stuff from *both* usernode.module (Picture, Created time) and views_profile.inc (Custom fields like Country, Interests).

I'd love to provide a link, but I'm having an issue where the view isn't spitting out any content for anonymous users. merlinofchaos, is this a Views-wide bug? I know you're out of town.

Next, I want to be able to really change the look of this view, and it's currently not as flexible as I'd love for it to be.

Also, the usernode that usernames now link to doesn't include the custom profile fields and other information I would get on the default profile pages. fago?

Getting close. Can anyone help w/ the last mile? I think this would benefit alot of people.

@usernode: you may use the Usernode: Name field, which links to the normal drupal user page as default.

Thanks fago. Using Usernode: Name does indeed list the usernames, but they're not linked.

if you want a link you have to set the handler for this field to "themed userlink" in the views edit page.

That'd be cool, fago, but no handler options are available for the Usernode: Name field as far as I can tell.

I'm using v 1.19 of the usernode.module.

Thanks for the help.

--D

clear your cache and try again. (views caches a lot)

Hello,
Above states:
> I can't get all users with profiles to show up.

> views is based on the assumption that nodes are selected. its base table from the database is hence the node table. most likely, the users not showing up have not created any content so far. is that possible? currently views_profile only finds users that have created some content (ie an entry with their uid in the node table)

I'm new at this and I need to create tables from a load of user profiles. Unfortunately most of the members won't be creating content immediatly. Is there a way around this? Is there a patch or module that creates a page for each profile as if it were content from the user? Thanks,
John

Hello again,
Yahoo! I just found the answer to my request (#28) above: http://drupal.org/node/68360
John

I was hoping there'd have been some more work on this.

I've gone ahead and committed it so that future fixes can be simple patches, and more people will likely be involved because this could theoretically be a very big deal.

One very important fix that needs to be done: When profile fields are changed or updated via the profile admin page, views' cache needs to be invalidated. It should be relatively trivial. Anyone want to roll a patch?

Please roll said patch as a separate issue (but reference this one!)

I don't think there is a hook when profile fields are added/removed so the best way to notice this event and clear views cache is to add submit handlers to the profile add and delete forms.

it doesn't look like this was commited to HEAD not the 4.7 branch... which would be fine if this bug hadn't been marked as 4.7...
http://cvs.drupal.org/viewcvs/drupal/contributions/modules/views/modules...
maybe the tags are just screwy

I haven't moved the tag up; I didn't actually notice the version on the queue.

I plan to move the tag up fairly soon, I just wanted to make sure all the changes I put in were stable before catching 4.7 up.

This has been live for a little bit now

how does this work? I dont see any extra fields (I was expecting to see profile fields) under arguments or filters when I add a view

erm... I´m asking the same thing here that our vrao fellow.
I don´t see profile fields... maybe I´m doing something wrong? Or didn´t do some step?
(I´ve got installed the last version of views for 4.7)

Thanks!!

Rosamunda

I don't see any change at all to my drupal site either... also, the instructions are very unclear. I uploaded the file to modules/views/views_profile.inc but I don't understand how adding a file would do anything if there is no call to include it? Was this file really meant for v 4.7.x? It's also not mentioned anywhere in the original post. Any help apprecited!

Jen

Oh good grief, people.

views_profile.inc has been with Views since October. It's in every officially released version. Why you'd take a closed issue and re-open it with some cryptic message is beyond me, but it's a bad way to get help.

If you want help, open a support issue. Clearly state what it is you're asking.

DO NOT take over closed issues.

DO NOT change the title of an issue to something inane.

These things piss me off a lot.

ok, I'm sorry. I'm not trying to open a closed issue, but when I did a search on the drupal site for views_profile I only got 2 results, this page, and one referring to this page. It looked to me like the issue wasn't resolved, so - I asked again. How do I know where to look for actual resolutions?

(FYI) What it is I'm asking: How do I get profile Fields to appear as an option in the views "fields" drop-down?

Jen
---
Oh good grief, people. views_profile.inc has been with Views since October. It's in every officially released version. Why you'd take a closed issue and re-open it with some cryptic message is beyond me, but it's a bad way to get help. If you want help, open a support issue. Clearly state what it is you're asking. DO NOT take over closed issues. DO NOT change the title of an issue to something inane. These things piss me off a lot.

jenlampton, you must have skipped over the part where merlin said you should open up a support request.

He said to do that if there was a problem... and he also said that this had already been resolved, hence, no real problem. So - I was just elaborating for his benefit (or maybe just my own, since I don't think he really cares anyway)

I have opened a support request to address this: http://drupal.org/node/121164

And it's a good thing I create that support issue before I saw your crack about not really caring, because after that I certainly would not have bothered.

I spend hours of my life every month supporting this free product. It makes me happy when people use it and like it, but it also makes me unhappy when people fail to follow the requested procedure. It particularly makes me unhappy when people come here and insult me.

I'm sorry that you're having trouble with it. I don't pretend that it is perfect or bug free or everything it needs to be. That said, if you want help, there are proper avenues for that. Use them. I do help people when I have the time.

But do not come here and insult me.

I have absolutely positively no obligation to help you. I do it because I am proud of the software I create. No one pays me for this task, I do it in my spare time. So if I get impatient when procedure isn't followed, it's because my spare time is limited, and it upsets me that I have to spend my spare time getting people to simply do the right thing.

I am now finished with this issue.

no insult intended :-( sorry.