Hi,

First of all : hats of for this module. Its totally awesome and I can only imagine how many people you brought together with it. It totally rocks !!

When watching the video about ubercart I saw them do a very powerful concept where they attached a node a certain purchase.

For example, if I organised a Drupal workshop and allow people to register I want the firstname, lastname, whether they are vegaterian etc.
How they did it with ubercart was to couple a content type to the purchased item so that a drupal webmaster could easily create this content type with the required fields.

I know that with Signup you can edit the phptemplate_signup_user_form function to do the same thing but this requires a developer.

Think its really interesting how they did it

Here is more information :

http://drupal.org/project/uc_node_checkout
http://dc2009.drupalcon.org/session/advanced-ubercart-usage
http://www.lullabot.com/audiocast/podcast-76-ubercart-and-building-lulla...

Hope this helps, Tom

Comments

buckley’s picture

buckley commented
Title: Use a Conent Type for the subscription itself » Use a Content Type for the subscription itself
dww’s picture

dww
we/he/they
commented
Status: Active » Postponed

That'd be a massive re-write of many parts of the module. See http://groups.drupal.org/node/3430 for some of my thoughts on this matter years ago.

I think core fields in D7 might be the better way to solve the problem of #29568: Flexible number and type of fields...

buckley’s picture

buckley commented

Reading the 2 posts it seems the current approach is here for historical reasons and there are some worries about performance. Is this really an issue? I understand that comments are not nodes because its desirable to list 100's of comments on the same page. But who wants to list their sign-ups in such a way? The sign-ups are queried through views in the backoffice where full nodes are not required but certain fields (please take this with a grain of salt, I did not program even a module).

Im very satisfied with the current situation since though I know how to develop :)

Leveraging the knowledge about nodes that site builders posses (assuming they don't program) seems the way to go though IMO. I realy like the idea of everyting being a node/CCK'able and if comments are an exception so be it.

Maybe something to keep in the back of your mind if you refactor some code :)

dww’s picture

dww
we/he/they
commented

I hear you. The thing is that in all likelihood, in D7, signups will also be "CCK'able" in the sense that you can define your own fields on them. We'll see how it goes. Anyway, yeah, this has been in the back of my mind for well over 2 years... ;)