Better handling of title field

lonehorseend - December 21, 2008 - 22:06
Project:Rolespecific Node
Version:6.x-1.0-beta3
Component:User interface
Category:feature request
Priority:normal
Assigned:Lapino
Status:postponed (maintainer needs more info)
Description

Is there a way to make it so that the automatic creation of a node is selectable or at least handle the automatic title generation a little better. You see, right now I have CCK node type that asks for a person's name, but to have the automatic title generation for role specific nodes that made sense, I had to create a profile item called name. Therefore, I'm indirectly making my user enter their name twice, when I only want them to enter it once.

#1

Lapino - December 22, 2008 - 22:14

Could you explain how you plan on using this module a bit better please, because I'm not entirely sure I understand your goals. Do you want your users to be able to enter this data on registration or first login or something similar?

#2

Lapino - December 22, 2008 - 22:15
Assigned to:Anonymous» Lapino
Status:active» postponed (maintainer needs more info)

#3

lonehorseend - December 23, 2008 - 05:29

I'm trying to set up a site that sells services, items, and memberships, has a mailing list, and does events with volunteer signups. I'm actually going to be using the sign up module for a CCK created event type. The site has free roles and paid roles. The paid roles are assigned through Ubercart with an 1 year expiration date. The free roles are either assigned by the administrator or by the user when initially sign up at the site through Auto Assign Role.

All roles are set up to use content profile to create a content type specific for that role. The content types eventually become nodes that are searchable by other users through views and published / unpublished automatically based on the roles assignment / renewal through Ubercart, if they are a paid, or an administrative action, if they are free. Since they content types are created by CCK, they need at least have a title and I renamed that field name.

Role specific nodes seemed the missing piece I needed to handle the unpublishing / publishing part for the nodes, because I couldn't see a way to do it through the conditional actions of Ubercart or the triggers and actions of Drupal, or even rules (formerly workflow-ng), which is no longer going to be used by Ubercart because they are developing conditional actions.

Where I'm having a problem with the title is the fact that the choices I saw for it was either the username or the email. And well, I need my user's name. Role specific node only recognize any fields assigned to the profile and not the content type.

So basically if I have a person buy a membership, they would be filling out their name during registration through Profile, then once again if they decided to buy a membership for their billing address, and one final time if when they field out their profile content type. I'd like to eliminate at least one of these.

 
 

Drupal is a registered trademark of Dries Buytaert.