Posted by fago on April 30, 2007 at 11:51am
I'm happy to announce nodeprofile 5.x 1.1!
Thanks to the great subform element API module, which I wrote originally for pageroute, it was quite easy to implement some great new features for the node profile module, which make building simple node profiles a lot easier. So node profile 1.1 features
- configurable user edit categories integration - edit a simple nodeprofile like a core profile
- configurable node profile display integration on the user's (my account) page or - if used - also on the usernode
- configurable user registration integration
- easy integration of a nodeprofile in any theme
You can find the settings to this new features in the also new per content type node profile settings - just edit your node profile content type and click on the new "Node Profile" tab.
Read more about the new features on http://more.zites.net/nodeprofile_1-1
Comments
Thank you for your profile-related modules
Just a short note to say thanks for your work on this and the other profile-related modules.
I'm playing around a bit with them now and will be referring to the helpful tutorial you posted over on drupal.org.
The neat thing about Drupal 5.x and merlinofchaos' very helpful and practical Update status module is that I updated to your latest module (Node Profile 5.x-1.1) yesterday, 4/29. But thanks for the heads up for anyone not using the Update status module.
Things just keep getting better with Drupal! Thanks again for your work and your helpful replies to everyone here on g.d.o.
Walt Esquivel, MBA; MA; President, Wellness Corps; Captain, USMC (Veteran)
$50 Hosting Discount Helps Projects Needing Financing
Walt Esquivel, MBA; MA; President, Wellness Corps; Captain, USMC (Veteran)
$50 Hosting Discount Helps Projects Needing Financing
great that you like it
great that you like it :)
However I've to update the linked handbook documentation to make use of the new features :)
Dagnabbit!!!
...you got it done before I could work out how the registration was going to work.
Fantastic, thanks, and right on time. I have 9 days to be live on my site and I was needing that before going live.
Jock
tears are in my eyes right now
i have 11 hours to a live site that will use this. i loooooooooooooooooove you guys!
Now you got me rethinking...
I've been working with the usernode directly since adding in nodeprofile seemed like unnecessary overhead and I was willing to live with the caveats. Now you've got me rethinking how I want to do profiles because this new release sounds yummy. LOL!
All these profile options are making my head spin... There's your usernode and nodeprofile and the built in profile and people keep suggesting using bio with and without usernode...
I'm going to have to take a look at everything again. Once I've actually got users on my site, I don't want to be switching because there's no good way to transfer data from one CCK type to another. :(
Thanks,
Michelle
...you're not using CiviCRM
...you're not using CiviCRM then?
That adds yet another option for capturing profile information!
Nope
Thank goodness, I guess, my head is spinning enough. ;)
Michelle
of course my suggestion is,
of course my suggestion is, as it always was, to use the node profile module :)
Anyway switching shouldn't be so hard. Nodeprofile can mark any content type as user profile (except usernodes (:P) as this would result in an endless loop) - as long there is not more than one node per user there won't be any problems if you do this with existing data.
I think with bio it's also possible to configure an existing content type.
Well, that's the problem :)
Currently all my data is in the usernode itself. At the time I started this, I didn't find any benefit to using the nodeprofile instead of just the usernode, so that's the route I went. The fields themselves will be easy to transfer to a nodeprofile but the data won't. I only have a couple of users so it's no big deal right now but it does mean I need to decide what I'm doing before people start using my site.
I'm currently looking through all the options (see http://dev.shellmultimedia.com/node/42 if you're interested). I was surprised at how versatile the built in profile module is, but I've got too much invested in usernode to abandon it now. The main wild card for me right now is bio or nodeprofile. I just started looking at bio, so I don't know, yet, what the pros and cons are.
And some day I'll actually finish my all encompassing profile tutorial... LOL
Michelle
ah interesting. You could
ah interesting.
You could also consider nodeprofile together with pageroute, which actually enables you to build another different UI and way to fill out the profile :) - it's very flexible.
the utility of usernode
is there still value having usernode?
afaict, if i'm using nodeprofile to embed content types into the user page AND nodeprofile adds profile content types to the registraton process, there's not necessarily a need for usernode.
the only thing i was really using usernode for before was the automatic creation of node profile nodes.
for me personally, usernode
for me personally, usernode is useful in particular in conjunction with views.
I also like it for building a public representation page of a user, while I keep the user page for private things.
However, for me that was so even before nodeprofile 1.1 :)
maintenance
it's also the case that usernode still handles deletion of usernodes and unpublishing of usernodes (and the associated nodeprofiles) when the user is deleted or blocked, no?
i haven't built my search yet. perhaps when i do i'll discover that i should have spent my effort theming the usernode instead of theming the profile page...
of course usernode does
of course usernode does still handle that.
theme profile nodes is a good idea for sure. You can still show the themed profile node easily at the usernode.