Profiles as nodes

Drupal developer | Brandcircle

binutz — Fri, 05 Sep 2008 07:07:28 +0000

We are looking for an experienced Drupal developer / Company preferably in an around Chennai to carry out a couple of Drupal development projects. The requirement is urgent.

.Please contact me at binutz@yahoo.com

Profiles as nodes

Hide field by expired author role

Liliplanet — Fri, 29 Aug 2008 09:18:09 +0000

Hi All,

Hope you are very well.

What I would like is that say when a Platinum member role expires, it hides their own specific content.

This works that if you are a Platinum member, you are able to view this field.

<?php if (user_access('Platinum')): ?>
<div class="field field-type-text field-field-amount">
  <div class="field-items">
      <div class="field-item">Amount: <?php print $node->field_amount[0]['view'] ?></div>
  </div>
</div>

But I would like that if you were a Platinum member before and it is expired, not to show the fields that you were able to previously add as a Platinum member. So hide the field if you are the author of the Platinum field, but your role has expired.

Is that possible please?

Would most appreciate any help, and thank you.
Lilian

Profiles as nodes

redirecting user to node ...

Liliplanet — Wed, 27 Aug 2008 18:47:35 +0000

Hi All,

Just a little confused here and perhaps a question for Michelle :)

As many links i.e 'add ... nodereview, flag, etc' fall automatically in the links of nodes of your content types, why do we redirect the content type 'profile' to the usernode? as in node-profile.tpl.php as follows:

<?php
// We don't ever want to go to the nodeprofile itself. Always redirect to the user page.
if (arg(0) == "node") { 
  drupal_goto("user/$node->uid", NULL, NULL, 301);
}
?>

then in node-usernode.tpl.php we:

<?php
// We don't ever want to go to the usernode itself. Always redirect to the user page.
drupal_goto("user/$node->uid", NULL, NULL, 301)
?>

Should we not always be redirecting the usernode to the content type 'profile' (nodeprofile)? The problems I've been having is we have to manually insert the links on node-profile.tpl.php such as 'add to buddylist, review this node, flag this content, etc' which all appear easily on any other node content type (and some it's not possible at all on the usernode).

Not only that, but the title of the node can then be a cleaner SEO, and not the username, but what we want specifically.

Have now reinstalled vanilla sites at least 17 times and think getting the hang of what plays with what, but it's just a niggling question in the back of my mind.

Perhaps any clarification on this .. what are the benefits of going to the usernode instead of the content type 'profile'?
I think it's a problem that Drupal does not have a profile solution that is compatible with views and as above, we have to use redirects plus creating a double entry for firstly usernode and then the nodeprofile. Surely it could be one basic module (as the previous profile.module) but with views support and then able to add more content types as a nodeprofile.

I'm totally appreciative of the amazing capabilities of Drupal, and speaking out of turn as I do not really develop, but honestly trying not to bloat entries on my website, and would most appreciate any input.

Look forward to any reply.
Lilian

Profiles as nodes

How to redirect link to /node/% to /user/% ?

xenode — Fri, 22 Aug 2008 04:14:23 +0000

My setup is Drupal 5.10 and the latest versions of:

usernode, node profile, node family, imagefield, imagecache, Views, CCK

I am using the above modules to create userprofiles, whose pictures are displayed in a gallery format using imagefield+imagecache+views. My user profiles are taken over using michelle's template.php snippet, featured in her userprofiles #1 tutorial. Every /user/% looks just like its corresponding /node/%.

In views I add the field "field_image_field" and "Node: Author Name". This creates a photo gallery, with the user's name under each image.

The "Node: Author Name" links to /user/%. This is good.

The "field_image_field" is set to "Handler: Show first values only", and "thumb as link to node". It links to /node/%. This is not good.

I want it to link to /user/%. Unfortunately, in views under "option", there is no way to link "thumb as link to user".

How do I link each image_field to the /user/% ?

Please help.

Profiles as nodes

Permissions for Node Profile

mcsnolte — Mon, 11 Aug 2008 15:42:26 +0000

For the site we're creating we would like users to only be able to edit their Node Profile node, but no need to create one (our import tool creates a profile for them). However, it looks like this is not possible since it seems you need permission to "Create" the profile in order to edit it. Has any found a way to get around this?

Profiles as nodes

How do you set up user profiles?

specmav — Mon, 07 Jul 2008 06:42:28 +0000

With the vast amount of profile as nodes implementations, how do you set up your own profiles on your sites?

What I am really looking for are what modules are deprecated and rarely used to the more flexible and complete user profile solution.

Does anyone who is serious about creating complex and dynamic profile(s) ever use profile.module and if so, why?

Do you use any custom coding, and if yes then for what?

I am really looking forward to creating a profile solution for one of my sites and I want to maintain a clean back end and flexibility.

So here is a good time to show off your profiles and tell people how you made them?

Profiles as nodes

Format and line breaks in multi-line text

Liliplanet — Fri, 23 May 2008 10:01:43 +0000

Hi!

I can imagine this is pretty easy, but have done an extensive search and :) cannot find a solution please ..

Inserting a multi-line text in node-profile.tpl.php with field_introduction and field_detailed_profile just prints as text without line breaks or automatic links.

<br><div><center><b><h2><?php print $node->field_introduction[0]['value'] ?></h2></b></center></div>
<br><div><?php print $node->field_detailed_profile[0]['value'] ?></div>

Please how can I have the text format correctly with automatic links?

Would most appreciate any help and thank you.
Lilian

Profiles as nodes

Profiles as nodes and GMAP

peashooter — Fri, 23 May 2008 08:51:48 +0000

Hello all,

I'm looking to switch my user profiles to nodes because it gives me more flexibility with gmap.

Unless my user profiles are nodes, I can't use views to select them (or subsets of them) to display on a google map.

Has anyone had any experience of creating user location maps with nodeprofile/userprofile and gmap?

I've hesitated until now to change profiles to nodes. I'm not so worried about performance (low traffic site) but I don't want clashes with all my other installed modules!

crossing my fingers...

Cheers

Profiles as nodes

MySite + CCK + Panels + Users + Profiles + Account Mgmt + AdvProfile + lots more = one BRAVE new user* world

sdboyer — Sun, 11 May 2008 03:13:08 +0000

There are a ton of great & ongoing discussions about different ways to try to bridge the gap between some of the existing methods of organizing and presenting user data. The ones that I'm most aware of - and please do forgive me if I've missed something big here - are the ongoing attempts to bring Bio and Nodeprofile together, the discussion about integrating MySite and Panels, not to mention Advprofile, which is in itself an attempt to unify a number of disparate modules. Michelle and I have been talking for a while about Advprofile in particular, but the other day, the ball really got rolling and we covered a lot of ground. I need to finish the release of Panels2, so this isn't something that I'm going to be working on RIGHT away, but Michelle agreed that we should post up the transcript of our conversation so that we've got as long & far a running head start as possible before we get moving.

The discussion started with Michelle's pastebinning of her 'Advanced Profile Kit - Grand Vision,' which was as follows:

Takes over the user view tab
Admin chooses what content can be on profile pages.
User has panels-lite interface

Allows choosing from admin approved layouts
Allows adding content into panels
Content is restricted to what the admin has marked as allowed
For each panel, user can choose whether it is visible to all, buddies only*, or just themselves
CCK fields/fieldgroups content has an edit button that allows user to change the underlying content

What about other whole panels (displays?)? Does it make sense for the user to be able to add more? Do any SN sites allow more than one "page" for a user profile?
User should be able to upload their profile picture here instead of the account tab

And we were off and running from there. The numbers in my initial responses refer to the numbers in the above list.

===============
TRANSCRIPT FOLLOWS:

May 03 21:15:33 sdboyer-laptop - May 03 21:16:41 sdboyer-laptop - May 03 21:17:15 sdboyer-laptop - May 03 21:17:43 sdboyer-laptop - May 03 21:17:46 Michelle - May 03 21:18:13 sdboyer-laptop - May 03 21:18:30 sdboyer-laptop - May 03 21:20:54 Michelle - May 03 21:20:59 sdboyer - May 03 21:21:28 sdboyer - May 03 21:21:39 Michelle - May 03 21:22:13 Michelle - May 03 21:22:27 Michelle - May 03 21:22:35 Michelle - May 03 21:24:58 sdboyer - May 03 21:25:22 sdboyer - May 03 21:25:32 sdboyer - May 03 21:25:39 sdboyer - May 03 21:25:53 sdboyer - May 03 21:26:08 sdboyer - May 03 21:26:21 Michelle - May 03 21:26:23 sdboyer - May 03 21:26:41 sdboyer - May 03 21:26:57 sdboyer - May 03 21:27:09 Michelle - May 03 21:27:11 sdboyer - May 03 21:27:29 sdboyer - May 03 21:27:39 sdboyer - May 03 21:27:47 sdboyer - May 03 21:27:50 sdboyer - May 03 21:27:55 sdboyer - May 03 21:28:10 sdboyer - May 03 21:28:17 Michelle - May 03 21:28:24 Michelle - May 03 21:28:36 Michelle - May 03 21:28:42 sdboyer - May 03 21:28:47 sdboyer - May 03 21:29:11 Michelle - May 03 21:29:15 sdboyer - May 03 21:29:25 sdboyer - May 03 21:29:26 Michelle - May 03 21:29:27 Michelle - May 03 21:29:42 sdboyer - May 03 21:30:08 Michelle - May 03 21:30:16 sdboyer - May 03 21:30:30 sdboyer - May 03 21:30:34 Michelle - May 03 21:30:41 Michelle - May 03 21:30:50 sdboyer - May 03 21:31:18 sdboyer - May 03 21:31:22 sdboyer - May 03 21:31:32 sdboyer - May 03 21:31:39 Michelle - May 03 21:31:45 Michelle - May 03 21:31:49 sdboyer - May 03 21:31:56 Michelle - May 03 21:32:13 sdboyer - May 03 21:32:16 Michelle - May 03 21:32:23 sdboyer - May 03 21:32:26 sdboyer - May 03 21:32:30 Michelle - May 03 21:32:40 sdboyer - May 03 21:32:46 Michelle - May 03 21:33:16 sdboyer - May 03 21:33:49 Michelle - May 03 21:34:19 sdboyer - May 03 21:34:28 Michelle - May 03 21:35:39 sdboyer - May 03 21:36:07 sdboyer - May 03 21:36:32 Michelle - May 03 21:36:45 Michelle - May 03 21:36:52 sdboyer - May 03 21:37:00 sdboyer - May 03 21:38:07 Michelle - May 03 21:38:07 sdboyer - May 03 21:38:42 sdboyer - May 03 21:38:43 sdboyer - May 03 21:39:05 sdboyer - May 03 21:39:27 Michelle - May 03 21:39:45 sdboyer - May 03 21:40:00 Michelle - May 03 21:40:15 sdboyer - May 03 21:40:16 Michelle - May 03 21:41:44 sdboyer - May 03 21:41:48 sdboyer - May 03 21:42:12 sdboyer - May 03 21:42:39 Michelle - May 03 21:43:07 sdboyer - May 03 21:43:24 sdboyer - May 03 21:43:33 sdboyer - May 03 21:43:52 Michelle - May 03 21:44:21 Michelle - May 03 21:44:28 sdboyer - May 03 21:44:42 sdboyer - May 03 21:44:49 sdboyer - May 03 21:45:31 sdboyer - May 03 21:46:01 sdboyer - May 03 21:46:14 sdboyer - May 03 21:46:23 sdboyer - May 03 21:46:45 sdboyer - May 03 21:46:57 Michelle - May 03 21:46:58 sdboyer - May 03 21:47:09 sdboyer - May 03 21:47:29 Michelle - May 03 21:47:30 sdboyer - May 03 21:47:43 Michelle - May 03 21:48:04 sdboyer - May 03 21:48:13 sdboyer - May 03 21:48:26 sdboyer - May 03 21:48:32 sdboyer - May 03 21:48:40 sdboyer - May 03 21:48:44 sdboyer - May 03 21:48:45 Michelle - May 03 21:48:57 sdboyer - May 03 21:48:58 Michelle - May 03 21:49:02 sdboyer - May 03 21:49:13 sdboyer - May 03 21:49:24 sdboyer - May 03 21:49:27 Michelle - May 03 21:49:37 sdboyer - May 03 21:49:53 sdboyer - May 03 21:50:02 sdboyer - May 03 21:50:54 Michelle - May 03 21:51:00 sdboyer - May 03 21:51:02 Michelle - May 03 21:51:06 Michelle - May 03 21:51:08 sdboyer - May 03 21:51:14 sdboyer - May 03 21:51:23 sdboyer - May 03 21:51:34 sdboyer - May 03 21:51:40 sdboyer - May 03 21:52:11 sdboyer - May 03 21:52:12 Michelle - May 03 21:52:19 sdboyer - May 03 21:52:46 Michelle - May 03 21:52:55 sdboyer - May 03 21:53:05 sdboyer - May 03 21:53:18 Michelle - May 03 21:53:20 sdboyer - May 03 21:53:29 Michelle - May 03 21:53:36 sdboyer - May 03 21:53:39 Michelle - May 03 21:53:50 sdboyer - May 03 21:53:53 sdboyer - May 03 21:54:03 sdboyer - May 03 21:54:09 sdboyer - May 03 21:54:18 sdboyer - May 03 21:54:58 sdboyer - May 03 21:55:21 Michelle - May 03 21:55:32 Michelle - May 03 21:56:23 sdboyer - May 03 21:56:46 sdboyer - May 03 21:57:01 sdboyer - May 03 21:57:27 Michelle - May 03 21:58:33 sdboyer - May 03 21:58:51 sdboyer - May 03 21:59:02 sdboyer - May 03 21:59:03 Michelle - May 03 21:59:14 sdboyer - May 03 21:59:29 sdboyer - May 03 21:59:41 sdboyer - May 03 21:59:46 sdboyer - May 03 22:00:05 sdboyer - May 03 22:00:12 sdboyer - May 03 22:00:23 Michelle - May 03 22:00:26 sdboyer - May 03 22:00:38 sdboyer - May 03 22:00:39 Michelle - May 03 22:01:18 sdboyer - May 03 22:01:25 sdboyer - May 03 22:01:48 sdboyer - May 03 22:02:05 sdboyer - May 03 22:02:48 Michelle - May 03 22:02:52 sdboyer - May 03 22:03:31 sdboyer - 1, 2, 3.2, 3.3, 3.4, & 4 have all been implemented on some level somewhere before, and are known to be quite feasible - Ed. note: 3.4 is complete and has been committed for beta4
a panels-lite interface isn't something that's been really worked out in a consistent way yet
there are some existing tools that do pieces of it, but more work on our end really ought to be done to tie those elements together and make creating a reduced panels interface easily doable
3.1 is actually one of the first pieces of panels code i ever wrote, and i did a crappy job of it, but i'm rewriting it for beta4
Whoah, sorry, I was in another window. Catchingup
there'll be an api for it that works just like the other main api editing components - panels_edit(), panels_edit_layout(), panels_edit_layout_settings(), and the new one will be panels_edit_available_layouts() or something like that - Ed. note: completed and committed for beta4
as with calls to the panels_context_create*() and content_type functions, it'll return an array of allowed layouts as per what's been allowed somewhere else in the panels admin interface
Sounds like my "grand vision" has a lot of potential to happen
oh absolutely
3.3 is implemented right now, but the interface for it sucks and it's inflexible, improving it is on my list
As for how it is now, it's basicaly a panel page that overrides user/% and a bunch of minipanels / view panes
Bascially what I'm going for is the user looks at their profile page and can customize it right there on that page
Rather than going to other tabs to fill in bits of it
And having a static layout imposed on them
sorry, four things goin on
yeah, that is a trick that'd take some creative implementation of the UI
and would be new territory for the panels API
however
i do think that it's also the way that the panels-lite interface should be implemented
lemme see, what else did i miss on the list
Same here :) (4 things...)
3.5 is a little outside my expertise right now, i've just been awed-at-a-distance by the cck integration
i've never seen 5 done, but i absolutely can't imagine it being any problem whatsoever
now, as for 4
3.4 would be nice, but I can see that being a future phase
my personal thinking on that is this -
actually, it's probably less remote
b/c it's pretty much the model of og_panels/blueprints
other SN sites don't do it, true
or at least, not much
personally though, i think that's a mistake
b/c it really does tend to lead to this 'mash everything onto a single page' nastiness
I'm trying to think how that would look... You wouldn't want a top level tab for each panel page, I think...
Maybe subtabs on the main tab?
Using "panel page" loosely here
sure sure
i think it'd depend on who's looking at it
Hmm... true. Non admins and non user in question woudln't see so much
oh...man did i just get a crazy freakin awesome thought
hold that, finish this first :)
Espeically if you dropped the track/contact tabs
Yeah?
yeah, i think it's gonna be a question of how the other tabs get dealt with
So you'd go to blah.com/user and you'd see several profile tabs at the top level and nothing else unless you're that user or an admin...? That's not so bad maybe
clearly it makes sense to have some separation between the pure panels/profile/blueprints/fun tabs and the other ones
but yeah, i think that's part of the question
Or you have one tab named "profile" and subtabs under
Not sure which is better
to me, this comes back to one of those central questions i know we've talked about before
which is the difference between what might show up at the user/1 page itself, as it's currently defined, versus what shows up at this profile-as-node thing instead
are those the same thing?
or are they different, kinda like account vs. profile?
Well, in advprofile's case, the actual node redirects to /user
And then the node is just part of what's shown
right
For advprofile, the node is jsut a holder for the data
and i mostly just used the url as a means of pointing out that, by default, that's NOT a node
Actually, the holder is irrelevent. You could use it with core profile if you wanted
yep yep
painful though that might be :P
Heh, yeah
my fundamental issue here is the more kinda abstract theoretical one
Basically, I want advprofile tied to the /user page and not care what exactly is in it
do we separate accounts from profiles, when do we do it - if we do by default, do we allow reintegration? if we don't by default, do we allow integration?
Ok, you just lost me
hrm, ok, lemme try to paint the three distinct cases that i see
Ok
case 1 - user/1 contains more or less the same sort of stuff that we see in it now. it's primarily geared towards the user him/herself for the purposes of account management
at the same time, profile/1 is one of this nifty-fangled panelized profiles we're so keen on
I'm not too worried about the URL as long as theme_username points to the profile, not the for the user thing
Basically, anyone wanting to look at the user should see the profile
again, just using the urls as a means of concretely differentiating between what's a node and what isn't
not that that's the best way of doing it, heh
Well, in my "vision", we're going beyond profiles as nodes... The node simply becomes a container to hold some of the profile data. The rest is gathered from other sources and brought together into a profile as page
case 2 - no big-expanded profile at all, all we've got is pretty much the user/1 page that ships with drupal now
i'm with ya on that, but i'm stuck back where i am because i see a data organization & consistency problem that i think needs to be resolved before a grander vision can be effectively realized
all imo
but you're right, i should stop calling em nodes, nodes isn't the point
I'm pretty open on this. I've got ideas, of course, but I'm up for collaboration, too, so any input you have is welcome
so yeah, case 2 is essentially similar to what we see on d.o right now
Yeah, case 2 is pretty icky, I think
indeed, BUT...well, i'll come back to that
Just dumping stuff on a page like that is no good
case 3 is more along the lines of what we're talking about - something that integrates the awesomeness of panelized profiles with all the stuff that used to appear and be used in the old case 2-style system
and the necessary result that we've got users able to control and lay out some, but not all, of what appears on their profile pages
from a programmatic angle, i don't think these really need to look all that different
That's always been a difficulty... by taking over the page, you lose what modules dump on it. Personally, though, I don't think modules dumping things on the user view tab is a good idea
i'm talking much more about the end-product - my thinking is that any given drupal site is going to want something that falls into one of the three categories, and so the system that eventually wins here is going to be the one that can easily accomodate each of these three outcomes
right, and it's often done pretty badly, but
it's also not a functionality i think we can really justify eliminating
Well, if we just make a user profile "thing" which is basically a panels page but maybe something custom to this if needs be, then the site admin is free to give it whatever URL they like
I would set it to user/% by default but they coudl change it to profle/% or anything
yep
yeah, my hope with all this
and this more or less constitutes the second part of my comments on that list
is that we'd see advprofile grow into something that accomodates all three of these cases, which i think you can also sort of divide along 'private', 'semi-public', and 'public/almost all public'
that advprofile would be able to handle splitting some content to one URL and the other content to another (if needed)
and it would also provide a system for structuring whatever stuff other modules want to dump onto the user page
so that it's dumped in a well-organized, coherent way
or, in case 1, it's simply dumped into it's own separate space
Hmm... I dont' actually know how stuff is added to the page now. If it's something that could be intercepted, that's not a bad idea to grab and redirect it
...a space which also happens to be nice and well-organized :)
i'm glad you think so
My concern is that it's just form_alter'd on... Can that be grabbed?
basically my only point here is that you can't really think about doing profiles effectively WITHOUT having a good system for handling everything else
True. I've been sort of glossing over that so far
i think you actually already cited the solution to that
what we're talking about aren't nodes
they also aren't whatever-the-hell-user/# is right now
they're...panels!
they live in that ethereal space that panels is in :)
consequently
Hehe
it's COMPLETELY under your control to determine what content does or does not appear, where it appears, etc.
Back to the "panels profiles" idea
yep
i (big surprise) think it's the right solution
just that it needs to be built & scaled in the right way to accomodate all these possibilities transparently
So we encapsulate the whole profile, including what modules want to dump on it, into our "panels profile" and that can be put at whatever path the admin likes
yep, or
it can be split into two separate paths, one for the account-y info and the other for the profile-y info
whatever floats their boat
Yeah, I think there's a line there between what is "settings" and what is "profiles"
dealing with the results of the original user profile system & such then just reduces to a question of designing some gnarly panels content_types
That's why I want to move the avatar upload
That's a profile thing, I think
for sure
but of course, it's also subjective
or rather
maybe not subjective, but dependent on the context of your website
i can see valid arguments being made both ways
which is why i think we're best off with a solution where that decision is made by the admin in setting up their profile/account system
True... So it needs to be admin decidable
zactamundo
Ideally, I'd like to have a "wizard" install for this because people already think advprofile is too hard to set up
yeah, i'm 200% with you on that
i had plenty of trouble with it the first time around
Given how smart you are, that's scary...
not your fault, just a whole bunch of crap getting woven together
I've done my best to simplify it but, yeah, there's a lot to it
yep, there's really just no way around it
I changed the name to "kit" to try and get that across
i was trying to remember if that was there before or not
good call
but...hopefully
if we can sort out this more basic infrastructure question
then a LOT of this other stuff will fall into place
i really am convinced that part of the reason these discussions go around and around in circles is b/c there's no widely understood delineation between what constitutes a profile and what constitutes an account page
I just hope this doesn't get too beyond my skills... So far, advprofile is rather simple as far as coding goes. It's mostly panels exports
Yeah, that is a difficulty
which is why i also think that creating that distinction programmatically, and doing it in a way that explicitly highlights it being a subjective thing, will not only be good for individual folks tryin to make all this work, but also for that whole discussion
yeah, there is a lot to all this, i'm certainly not saying you should take it all on on your own :)
in my mind, there are a couple discrete parts:
You're welcome to be a co-maintainer... Though you may confuse the hell out of me if you commit something since I really suck at cvs
i'd love to :) though i should hold off for at least a little while, probably until i get panels to rc
with some of this stuff, i'm effectively doing work that'd need to be done for this anywya
anyhoo, discrete steps:
Well, this is all pretty long term planning, anyway
1. the system for handling what is strictly 'profile' content, significant parts of which can be drawn from the og_panels & og_blueprints approach
though, to be certain, not all can be drawn from there
actually...hmm
i'm liking this
here's a basic reality: there will ALWAYS be some kind of account page
somewhere that the user can, at minimum, change their password and email address
Yes, definitely for basic settings
right
which means we're assured that we're absolutely always gonna have that one
My original plan was to merge that but I've since realized htat makes no sense
which means that the thing we should start with is the account panels_page/display/thingamabobber
b/c we know it'll always be there
for rendering speed purposes, we can probably even just have that operate out of straight code by default, then switch to the db if customizations are needed
but basically, what we're talking about there is...CONTEXT!
Heh
the essential choice that we present to admins is whether a given user-related content_type should be given an 'account' context or a 'profile' context
sorry, at this point my brain's spinning and i'm just spouting ideas left and right

May 03 22:04:31 sdboyer - those that're given the account context will be added somewhere to the account display, and that's something only admins control
May 03 22:04:34 Michelle - No problem :)
May 03 22:04:58 sdboyer - whereas things are a bunch more wide open for the content_type with profile contexts
May 03 22:05:05 Michelle - I'm glad to have you on this, even if I have to wait. I think advprofile will be much better with your help:)
May 03 22:05:25 sdboyer - i hope so :)
May 03 22:05:42 sdboyer - from there...there's a subcategorization in the context
May 03 22:06:00 sdboyer - either it's a 'strict' profile item, one that's at least somewhat editable by the user
May 03 22:06:03 Michelle - I wonder if we should attempt this in D5 or wait until D6? What do you think about that?
May 03 22:06:15 sdboyer - two things come to mind with that
May 03 22:06:43 sdboyer - one is that by the time i think the moons have really aligned on this, there's going to be a lot more work going on in d6
May 03 22:07:20 sdboyer - plus there's existing work towards a unified model for users already happening in d6
May 03 22:07:32 sdboyer - but, i think that most of what we're talking about here is fundamentally core-version independent
May 03 22:07:39 Michelle - Yeah, the whole panels/mysite thing factors into this
May 03 22:07:40 sdboyer - or at least 5 v 6 independent
May 03 22:07:43 sdboyer - for sure
May 03 22:07:46 sdboyer - ahh yeah
May 03 22:07:48 sdboyer - for suuuure
May 03 22:08:03 sdboyer - RIGHT, that's the other thing that an account is
May 03 22:08:09 Michelle - I'm thinking waiting for D6 on this would be best.
May 03 22:08:14 sdboyer - it's a dashboard for the user
May 03 22:08:16 Michelle - advprofile 2.x ;)
May 03 22:08:27 sdboyer - sounds oh-so-sweet :)
May 03 22:08:38 sdboyer - my thinking, at least when it comes to how my own time is gonna work on this
May 03 22:09:03 sdboyer - is that there are some big pieces that are core version independent, and i'm probably going to want to work on them as the other stuff i'm doing coincides with it
May 03 22:09:05 Michelle - I'll probably do a straight port of whatever I have when panels D6 is ready just to keep people happy for a while and then switch gears and do the "vision"
May 03 22:09:12 sdboyer - for sure
May 03 22:09:53 Michelle - Whatever you would like to work on helps :)
May 03 22:09:57 sdboyer - b/c honestly, i think a lot of this is going to be about getting our minds around this clearer way of thinking about the differences between these types of user areas
May 03 22:10:06 sdboyer - ahh phone, sec
May 03 22:10:41 sdboyer - ok
May 03 22:10:45 sdboyer - so yeah
May 03 22:10:51 sdboyer - ahh right, i was trying to make a discrete list
May 03 22:11:53 sdboyer - 2. creating an API, probably one largely based on an extension of panels, that enables other module developers to EASILY plug in to either the 'account' or the 'profile' end of the system
May 03 22:12:47 Michelle - That woudl be awesome
May 03 22:13:03 sdboyer - 3. being at least a little pro-active about where & how the data for users is getting stored, b/c i can see that turning into a hellish performance nightmare if there isn't some forethought
May 03 22:13:51 Michelle - Hmm... 3 might be hard. I like keeping it agnostic as far as bio/nodeprofile/content profile/core profile/whatever
May 03 22:14:05 sdboyer - yeah, you're probably right
May 03 22:14:12 sdboyer - i don't even know exactly what i'm thinking of when i say that
May 03 22:15:05 sdboyer - i've just got this picture of potentially complex combinations resulting in snarled runs of nasty, hairy queries that could've been easily made more unified by some structure at the outset
May 03 22:15:24 sdboyer - but really, that'll take time no matter how we slice it
May 03 22:15:48 Michelle - Heh
May 03 22:16:00 sdboyer - coming in with a new API and saying that everyone oughtta use it - "so rewrite all your data structures right now, guys!" would TOTALLY meet with a great response
May 03 22:16:08 Michelle - Panels lets you make really complex things easily. I found that out when my front page started going - 30 seconds
May 03 22:16:14 Michelle - LOL
May 03 22:16:21 sdboyer - yep, it sure does
May 03 22:16:39 sdboyer - which is why the need to work out a better caching system is going to get really big, really soon
May 03 22:17:15 sdboyer - all in all, though
May 03 22:17:18 sdboyer - maybe i'm delusional, but
May 03 22:17:21 Michelle - Yeah, definitely. Especially one that doesn't turn styles off for anon.

strong - === We broke for the night. Then, in the morning... ===/strong -

May 04 08:35:59 Michelle - sdboyer - One thing we didn't touch on is the notion of public profile vs "home page". That's a distinction I plan on having on my site. Users will have a "public face" which is currently done via advprofile and a customizable "home page" which gathers information useful to them as a landing page for my site. This is the realm MySite covers.
May 04 08:36:22 Michelle - So there is the question of whether these are both integrated into one package or remain seperate projects
May 04 08:36:40 Michelle - I actually can't stay and chat now but wanted to get that in your backscroll before I leave
May 04 08:36:44 Michelle - I'll be back in a few hours.
May 04 08:38:07 sdboyer - yeah, that's the realization that i started to have as it regards MySite, but that's the better way to put it, the user 'home page'
May 04 08:38:33 sdboyer - my first inclination is to say that we're probably safe collapsing the idea of the 'account' together with the 'home page'
May 04 08:39:03 sdboyer - because the real distinction that we're making here, imo, is between who this content is supposed to be facing - just the user, or the public
May 04 08:40:27 sdboyer - i imagine there'll be quibbling over terms with these things, but i think that if we're splitting the classification that way - information that's public-facing vs. information that's private-facing, and we build our two panel 'spaces' accordingly, then we'll be good
May 04 08:41:25 sdboyer - all we have to hard-code is that there are two panel-spaces per user, one private and one public, and then the admins choose which content goes into each
May 04 08:42:07 sdboyer - ahh, didn't see that you said 'landing page' at first, i think that's another good & often accurate way of thinking about the private space
May 04 08:59:39 Michelle - sdboyer - Actually back for a bit while I wait for hubby to get ready
May 04 08:59:57 Michelle - The only quibble I have with that is that MySite has an option to make your home page public
May 04 09:00:11 Michelle - So you can share your landing page with others... Do we keep that? Do people use that?
May 04 09:00:19 Michelle - That's a question that needs to be answered
May 04 09:00:34 Michelle - I, personally, would be fine with dropping it but MySite isn't my baby
May 04 09:08:56 sdboyer - right
May 04 09:09:01 sdboyer - and that is another question
May 04 09:09:18 sdboyer - i think there are two ways of answering it, both of which ought not be too difficult
May 04 09:09:51 Michelle - Two ways? Yes and No? :)
May 04 09:10:07 sdboyer - ;)
May 04 09:10:15 sdboyer - 1) we allow a 'peek'-style functionality wherein user/2 can grant, say, user/3 permission to view their landing page
May 04 09:10:50 sdboyer - and 2), we allow an 'export/copy'-style functionality wherein user/3 can, if properly permissioned, duplicate user/2's landing page onto his/her own landing page in whole or in part
May 04 09:11:06 Michelle - Oooh, that's a nifty idea
May 04 09:11:25 Michelle - For permissions, I favor the all/useronly/buddies model
May 04 09:11:26 sdboyer - i think that adequately covers it?
May 04 09:11:30 Michelle - Same as for the publich profile
May 04 09:11:44 Michelle - Granting specific UIDs sounds complicated
May 04 09:12:03 sdboyer - yeah, could well be, but at the same time
May 04 09:12:04 sdboyer - well
May 04 09:12:09 sdboyer - maybe we think of that part as an api
May 04 09:12:22 sdboyer - all buddies is really doing is selecting a group of uids
May 04 09:12:25 sdboyer - it just presents a ui for it
May 04 09:12:28 Michelle - True
May 04 09:12:34 sdboyer - but the case of the project maintainer stuff that merlin and i are pushing for right now
May 04 09:12:39 sdboyer - so we can assign issues to each other in panels
May 04 09:12:39 Michelle - UR complicates things, too
May 04 09:12:46 Michelle - So making that a generic api would help
May 04 09:12:50 sdboyer - zactly
May 04 09:13:01 sdboyer - and really, that shouldn't be hard to do at all
May 04 09:13:16 sdboyer - and i think could qualify as one of those 'having some foresight about organizing data' things :)
May 04 09:13:28 Michelle - Yeah, we definitely need to nail this down before coding
May 04 09:13:39 Michelle - This isn't a coding by the seat of your pants module
May 04 09:14:13 Michelle - I think hubby is just about ready to go so I only have a minuite or two
May 04 09:14:45 Michelle - Need to get merlinofchaos and Ken pulled in on this, too

Profiles as nodes

Am I doing this wrong?

heather — Wed, 07 May 2008 03:10:16 +0000

I decided to go with the Bio module, since I have one type of profile, and fairly simple needs.

When registering, people enter some basic contact info First Name, Last name and some info that will remain private, like phone number.
When their application is accepted, they can create their "profile"... But I want to be able to keep the First Name and Last Name they originally entered on their registration form.
I don't want them to use the "title" field for their name.

In the future I would like to use their last names as a way to sort through their profiles... so does this mean I will not be able to use the Views integration of the Bio module? The problem is that I don't want the users who haven't been accepted into the program to create their first and last name, since this content type is only for a specific user role...

Am I doing this all wrong?

Thanks in advance for any advice you can offer.

PS_ why does the text on this first page in the group get tinier and tinier and tinier?

Profiles as nodes

Bio Module and LDAP Integration

dperdue@drupal.org — Thu, 01 May 2008 01:36:24 +0000

At work I've got LDAP (Active Directory) integration working just fine. However, I also wanted to pull profile information (Job Title, Department, Phone Number, etc.) out of Active Directory so there's a central repository for that type of information.

Of course there's the LDAPdata which can integrate data from Active Directory into Profile module fields, but I wanted some solution to make Profiles into Nodes and integrating LDAP data into that node as CCK fields. I looked around for ideas or solutions to this problem but didn't find much. (Please if there's already a better solution, point me to that.)

New to Drupal module development, I hacked the below code together mostly from code stolen from the LDAPdata module. I would love some feedback on the code (since this is the first custom module I've done) as well as any ways to improve it. It's very hack-ish right now, with a lot of stuff hard coded into the module, and later on that could be pushed out into configuration pages and better tie-in to the LDAP module and CCK fields on the Bio node.

Here it is, any feedback is welcome.

<?php
$GLOBALS['ldapbio_ldap'] = new LDAPInterface();
/**
* Implements hook_user()
**/
function ldapbio_user($op, &$edit, &$user, $category = NULL) {
  switch($op) {
    case 'login':
      ldapbio_user_login($user);
      break;
    case 'after_update':
      ldapbio_user_login($user);
      break;
  }
}
/*************************************/
function ldapbio_user_login(&$user) {
  global $ldapbio_ldap;
  if (!$user->ldap_authentified) {
    return;
  } 
  if (!_ldapbio_ldap_init($user)) {
    return;
  }
  
  if (!$ldapbio_ldap->connect('user@example.com', 'password')) { //here's an account that has read rights to your LDAP
    watchdog('user', "User load: user $user->name's data could not be read in the LDAP directory", WATCHDOG_WARNING);
    return;
  }
  
  $entry = $ldapbio_ldap->retrieveAttributes($user->ldap_dn);
  
 $node = array( //here are the fields we want to replace with LDAP data
   "title" => $entry['displayname'][0],
   "promote" => 0,
   "uid" => $user->uid,
   "type" => 'bio',
   "status" => 1,
   "revision" =>1,
   "field_title" => array(0 => array('value' => $entry['title'][0])),
   "field_department" => array(0 => array('value' => $entry['department'][0])),
   "field_email" => array(0 => array('value' => strtolower($entry['mail'][0]))),
   "field_phone" => array(0 => array('value' => $entry['telephonenumber'][0])),
   "field_fax" => array(0 => array('value' => $entry['facsimiletelephonenumber'][0])),   
 );
 if ($row = db_fetch_object(db_query("SELECT nid FROM {bio} WHERE uid = '%s'", $user->uid))) { //this determines if there's already a bio node for this user, if so it updates it
    $node["nid"] = $row->nid;
 }
 if ($node = node_submit($node)) {
   node_save($node);
 }
}

Profiles as nodes

Use Bio now and later Profiles as Nodes

dotty@drupal.org — Mon, 14 Apr 2008 14:59:05 +0000

I really love this new module idea. Right now i am using Drupal 5,7. So,i can't use this module. I would like to use most likely Bio module or Node profile and collect the user information using CCK fields. Is it OK ? I mean i would like to use this module after my site code upgraded to 6.X. is that right approach ? or should i wieght ? My guess, once if i have this module, i just need to re-assain CCK fiels to content type related to this module. Am i right ...or too much imaginations ? Please advise me

Profiles as nodes

Insert node profile fields on a content type

Liliplanet — Sun, 02 Mar 2008 11:34:28 +0000

Hi,

Hope this message finds you very well.

I would like to have company information below press releases (content type = 'article'). In my node.tpl I have

<?php
 print $node->field_company[0]['value'] 
?>

, but it only shows up on the profile page and not underneath the article. mmm ..

node.tpl is currently as follows:

<div id="node-<?php print $node->nid; ?>" class="node<?php if ($sticky) { print ' sticky'; } ?><?php if (!$status) { print ' node-unpublished'; } ?> clear-block">
<?php if ($page == 0): ?>
<?php print $picture ?>
<h2><a href="<?php print $node_url ?>" title="<?php print $title ?>"><?php print $title ?></a></h2>
<?php endif; ?>
<div class="meta">
<?php if ($submitted): ?>
<span class="submitted"><?php print $submitted ?></span>
<?php endif; ?>
<?php if ($terms): ?>
<span class="terms"><?php print $terms ?></span>
<?php endif;?>
</div>
<div class="content">
<?php print $content ?>
</div>

<?php if ($page == 1): ?> <?php // Set up some variables to make the code easier to read without the confusion of which user is which. $loggedinuser = $GLOBALS['user']; $profileuser = user_load(array('uid' => $node->uid));?> <?php print theme("user_picture",$profileuser); ?><?php print $node->field_company[0]['value'] ?> <div><?php if ($links) { print $links; }?></div><?endif;?> </div>

Please, how can I insert nodeprofile information on another content type (not profile) and not to duplicate on the profile pages?

Most appreciate any help and thank you.
Lilian

Profiles as nodes

Replace profile.module fields with nodeprofile

Liliplanet — Tue, 26 Feb 2008 13:09:14 +0000

Hi Everyone,

I'm trying to install http://www.drupal.org/project/phplist, but for it to update in the external php installation, have to replace profile.module fields (which we don't use) with our nodeprofile fields ..

Would you be so kind to point me in the right direction in replacing the fields for my phplist please?

currently in the phplist.module

if (module_exists('profile)) {
    $form['general']['mapping'] = array(
      '#title' => 'Attribute mapping',
      '#type' => 'fieldset',
      '#description' => t('Use these settings to transfer first and last names from Drupal profiles to phpList.  If the phpList attributes do not already exist, they will be created.  Use the SYNCHRONISE NOW link to refresh all existing accounts.')
    );
    $form['general']['mapping']['phplist_profilefirstname'] = array(
      '#type' => 'textfield',
      '#title' => t('Drupal profile field for FIRST NAME'),
      '#default_value' => variable_get('phplist_profilefirstname', 'profile_')
    );
    $form['general']['mapping']['phplist_plfirstname'] = array(
      '#type' => 'textfield',
      '#title' => t('phpList FIRST NAME attribute'),
      '#default_value' => variable_get('phplist_plfirstname', 'First Name')
    );
    $form['general']['mapping']['phplist_profilelastname'] = array(
      '#type' => 'textfield',
      '#title' => t('Drupal profile field for LAST NAME'),
      '#default_value' => variable_get('phplist_profilelastname', 'profile_')
    );
    $form['general']['mapping']['phplist_pllastname'] = array(
      '#type' => 'textfield',
      '#title' => t('phpList LAST NAME attribute'),
      '#default_value' => variable_get('phplist_pllastname', 'Last Name')
    );

$form['general']['mapping']['phplist_roles'] = array( '#type' => 'checkbox', '#title' => t('Map non-system roles'), '#options' => array(0, 1), '#default_value' => variable_get('phplist_roles', 0), '#description' => t('Create phpList attributes for any custom user roles') ); }

and would like the following fields please :

In my Drupal database fields are as follows:

Table: drupal_content_type_profile

field_name_value
field_lastname_value
field_company_value
field_telephone_value
field_profession_value
field_country_value
etc.

Would most most appreciate your help on this.

Lilian

Profiles as nodes

How to create a view based on 'wanted' fields in a node profile?

luke76@drupal.org — Fri, 22 Feb 2008 11:53:31 +0000

Hi,

I hope I'm asking this in the right place. What I am trying to achieve is a swapping type site for housing e.g User A has 2 bedrooms, wants to swap for a 1 bedroom. I think I am right in using nodeprofile to make all users nodes and have added cck fields for what they have and what they want, but cannot for the life of me work out how to a create user-specific View which shows a list other user's profiles(nodeprofile) matched to the user's 'wanted' field. I suppose you could liken the functionality I'm looking for to something like a 'matching' or dating site.

I've looked at a range of sources but just can't seem to see anything that explains in non-coder terms how to make the views specific to the user/nodeprofile... this is only my third attempt at a drupal site after 2 very basic experiments so i hope this isn't too dumb a question. Would appreciate just a nudge or pointer to make sure i'm going in the right direction. Thanks for any help/ideas on this.

Profiles as nodes

Need advice on select from list by role

Liliplanet — Tue, 19 Feb 2008 08:08:54 +0000

Hi,

I'm trying to get my head around this and somehow just don't get it.

I have 2 roles, the normal 'authenticated' and a 'platinum' profile.

Both fill in the authenticated profile where they can select 1 listing (select list) in the business directory from a content type called 'directory'.

I would like the 'platinum role' to be able to choose 3 listings for the directory. How would I do that please?

Do I create a separate content type just for platinum users where they can choose their 3 listings in the directory or is there perhaps an easier way to do this?

Look so forward to any reply and thank you.
Lilian

Profiles as nodes

Different Profile Details per Subscribed Group

avdp@drupal.org — Thu, 14 Feb 2008 14:31:58 +0000

Hello all,
I am investigating Drupal and (probably) the Organic Groups to create a website.
What I would like to achieve is the following:
A person can be a member of different groups. I would like to make it possible that each user has a different profile (or different profile details visible) for each group.

It is meant for online collaboration for different projects (wiki, calender, etc); for each project a project member can have a different role. (For instance, for a project it could be interesting that the CEO is not visible as the CEO, to create less hierarchy; and for another project it could be vice-versa).
This would, for instance, also mean that a user has different profile images for different groups.
Next to this it would mean that when a user subscribes to a new group, the user is required to make a custom group profile.
Do you think this is possible, and would it require a lot of work / coding / modifying? What modules would I need?

All help is welcome,
thanks in advance

btw, I am pretty new to the Drupal communty, and after browsing the drupal site and information for some days, I am under the impression that this is the appropriate place for posting this question. If this is not the case please let me know

Profiles as nodes

Profile Advice

ChadH — Tue, 05 Feb 2008 20:10:19 +0000

Like many, I'm creating a networking site. While I'm new to Drupal, I've worked with PHP, HTML, CSS, etc. My question is what is the best way to allow a user to add multiple items to their profile? For example we'd like our users to add their work history to their profile. Since we can't tell how many jobs someone's had, we'd like the option for adding, editing and deleting each job individually (similar to LinkedIn). So do we create CCK modules to enter the information? Use nodes for each job and add a view for them on the profile page? We're currently looking at User Profile, but that can change. Any feedback would be helpful.

Thanks,
ChadH

Profiles as nodes

What is the difference between Node Profile and Usernode?

kirilius — Mon, 28 Jan 2008 06:06:07 +0000

What is the difference between Node Profile and Usernode modules?

1) Node Profile. According to its documentation: "This module builds user profiles as nodes, which opens the opportunity to use the Content Construction Kit (CCK)"

2) Usernode. Again the documentation says: "This module tries to make users nodes." And later on: "Use views to build user listings or even searches" and "Makes building of nodeprofiles easier"

It seems they both can help one create nodes out of user profiles and enhance them using CCK. Also they both integrate with Views. But isn't that already available just having a clean Drupal + CCK? Well the profiles will not be real nodes then but the new fields are still visible in the Views configurations.

Can somebody shed some light on this topic please?

Thanks!

Profiles as nodes

content profile 6.x prototype

fago@drupal.org — Fri, 25 Jan 2008 11:16:57 +0000

I'm creating a new thread for continuing the discussion of http://groups.drupal.org/node/8261.

I've just done some work and implemented a first prototype of the possible base module (variant 2) --> http://drupal.org/project/content_profile -> Test it!

This prototype allows to mark multiple content types as content profile, but tries to keep the code clean and simple. As nodeprofile had already the multiple content type stuff, I found it easier to start with it, and so I took the ongoing nodeprofile 6.x port, scraped features out of it, simplified the code and made it more extensible.

To make using the module the first time easier, the module comes with a default content type named "profile". It provides some settings per content type, which can be edited in a separate tab that appears when one edits a content type (like the CCK tabs) and supports displaying the content profile on the user page with different display styles.
The module comes with a set of useful functions, which should be useful for possible extension modules. Furthermore the settings system of the base module is extensible, so other modules can use it too.

It's a prototype, so don't expect it to be ready. (Although most things seems to already work.)

What needs work:
* Validation for only one profile node for site admins is missing
* This validation should work with translated nodes, this is also TODO.
* integrate missing features from bio module, e.g. link from the node to the user page
* and probably the themed output of the module on the user page.

I'm not good in theming, so the display stuff is basically the stuff from nodeprofile ported to 6.x, which I don't really like myself. So someone with more theming skills could be very helpful here.

So what do you think about? Should we build the base module out of this?
Should we go with the name "content profile"?

Profiles as nodes

Link from Views to User

Liliplanet — Sat, 19 Jan 2008 10:16:21 +0000

Hi Everyone,

I'm using Nodeprofile and Usernode, and all beautiful.

When I create tables in Views with the fields, and have tried :

link to node
node: view link
etc

it all links to the node url .... not the user/ url.

I've tried bio and advanced profile, all with the same results.

Please, how do I link from a table in Views (CCK content) to the user profile and not the node.

Would most appreciate any reply.

Lilian

Profiles as nodes

Profiles as nodes

Drupal developer | Brandcircle

Hide field by expired author role

redirecting user to node ...

How to redirect link to /node/% to /user/% ?

Permissions for Node Profile

How do you set up user profiles?

Format and line breaks in multi-line text

Profiles as nodes and GMAP

MySite + CCK + Panels + Users + Profiles + Account Mgmt + AdvProfile + lots more = one BRAVE new user* world

=============== TRANSCRIPT FOLLOWS:

Am I doing this wrong?

Bio Module and LDAP Integration

Use Bio now and later Profiles as Nodes

Insert node profile fields on a content type

Replace profile.module fields with nodeprofile

How to create a view based on 'wanted' fields in a node profile?

Need advice on select from list by role

Different Profile Details per Subscribed Group

Profile Advice

What is the difference between Node Profile and Usernode?

content profile 6.x prototype

Link from Views to User

===============
TRANSCRIPT FOLLOWS: