Re: [development] Getting both better internal and external APIs intoDrupal 7
On 12/29/2007 11:46:34 PM, Khalid Baheyeldin (kb@2bits.com) wrote:
Users as nodes has 3 modules at least in contrib:
- bio: the most straight forward of them. - node profile: a more complex way. - usernode: the original concept.
The need to customize how profiles look is the driver here, plus cck and views.
Core profile should go away soon, replaced by node + cck.
Most of this discussion is over my head but I wanted to comment on this. My upcoming Advanced Profile module uses Panels 2 for displaying the user profile on the view tab of the user page. It currently uses bio but will eventually be able to use bio, node profile, or even the core profile module. I'm designing it so it doesn't care where it gets the profile information from. What would be ideal is to have in core some way of optionally associating a user with a node type as bio does and also include in core a lightweight non-node solution for holding profile data for those who don't want a node for every user. Then people could use Panels 2 (which would be lovely to have in core someday) to display this "user profile object" as well as anything else they want on that page. For now, I'm making this possible in contrib, but having some of it in core would reduce the module dependency for this method. Michelle
On 30.Dec.2007, at 10:28, Michelle Cox wrote:
What would be ideal is to have in core some way of optionally associating a user with a node type as bio does and also include in core a lightweight non-node solution for holding profile data for those who don't want a node for every user. Then people could use Panels 2 (which would be lovely to have in core someday) to display this "user profile object" as well as anything else they want on that page.
HOT! +1 for including into core : CCK Bio Panels I need more coffee so I can find the notes of a wishlist I have been compiling for a while. I do know that ICONIZER and BUEditor would be ideal for those of us who would like Drupal to focus on usability and better design. I also understand the need to make the default distro lightweight. For that matter, I still believe there needs to be a serious push for different "default" distributions --and please, let's stop calling those "profiles" because it's confusing with the term "profile". Anyhow ... more ... coffee ... / liza Liza Sabater, Publisher www.culturekitchen.com www.dailygotham.com
I don't think bio is a good candidate for this, if the plan is to replace the profile module. Bio does not allow to put fields in the user registration form, which in my opinion is a required functionality for core. From my experience node profile does the cleanest of this (to make it core-worthy the node family dependency would need to be dropped of course). Wim blogdiva@culturekitchen.com wrote:
On 30.Dec.2007, at 10:28, Michelle Cox wrote:
What would be ideal is to have in core some way of optionally associating a user with a node type as bio does and also include in core a lightweight non-node solution for holding profile data for those who don't want a node for every user. Then people could use Panels 2 (which would be lovely to have in core someday) to display this "user profile object" as well as anything else they want on that page.
HOT!
+1 for including into core :
CCK Bio Panels
I need more coffee so I can find the notes of a wishlist I have been compiling for a while. I do know that ICONIZER and BUEditor would be ideal for those of us who would like Drupal to focus on usability and better design. I also understand the need to make the default distro lightweight. For that matter, I still believe there needs to be a serious push for different "default" distributions --and please, let's stop calling those "profiles" because it's confusing with the term "profile".
Anyhow ... more ... coffee ...
/ liza
Liza Sabater, Publisher www.culturekitchen.com www.dailygotham.com
FYI, as of the latest version of bio you can put fields on the registration form. Matt On Dec 30, 2007, at 11:46 AM, Wim Mostrey wrote:
I don't think bio is a good candidate for this, if the plan is to replace the profile module. Bio does not allow to put fields in the user registration form, which in my opinion is a required functionality for core. From my experience node profile does the cleanest of this (to make it core-worthy the node family dependency would need to be dropped of course).
Wim
blogdiva@culturekitchen.com wrote:
On 30.Dec.2007, at 10:28, Michelle Cox wrote:
What would be ideal is to have in core some way of optionally associating a user with a node type as bio does and also include in core a lightweight non-node solution for holding profile data for those who don't want a node for every user. Then people could use Panels 2 (which would be lovely to have in core someday) to display this "user profile object" as well as anything else they want on that page.
HOT!
+1 for including into core :
CCK Bio Panels
I need more coffee so I can find the notes of a wishlist I have been compiling for a while. I do know that ICONIZER and BUEditor would be ideal for those of us who would like Drupal to focus on usability and better design. I also understand the need to make the default distro lightweight. For that matter, I still believe there needs to be a serious push for different "default" distributions --and please, let's stop calling those "profiles" because it's confusing with the term "profile".
Anyhow ... more ... coffee ...
/ liza
Liza Sabater, Publisher www.culturekitchen.com www.dailygotham.com
Actually, I believe the current version does. Webchick added it for a site we were working on, and .. voila! ;-) On Dec 30, 2007, at 10:46 AM, Wim Mostrey wrote:
I don't think bio is a good candidate for this, if the plan is to replace the profile module. Bio does not allow to put fields in the user registration form, which in my opinion is a required functionality for core. From my experience node profile does the cleanest of this (to make it core-worthy the node family dependency would need to be dropped of course).
Wow amazing work :) I'll have to re-evaluate it then, thanks! Wim Jeff Eaton wrote:
Actually, I believe the current version does. Webchick added it for a site we were working on, and .. voila!
;-)
On Dec 30, 2007, at 10:46 AM, Wim Mostrey wrote:
I don't think bio is a good candidate for this, if the plan is to replace the profile module. Bio does not allow to put fields in the user registration form, which in my opinion is a required functionality for core. From my experience node profile does the cleanest of this (to make it core-worthy the node family dependency would need to be dropped of course).
participants (5)
-
blogdiva＠culturekitchen.com -
Jeff Eaton -
Matthew Farina -
Michelle Cox -
Wim Mostrey