By CyrilMazur on

Hi people,

I don't really know how to design my nodes and fields for my particular case. Here is the thing: in my e-commerce website, the backend is already coded in home-made php, and I want to use Drupal as my frontend.

Products are defined in the backend, and I use a webservice to transfer them to Drupal. The thing is, for each type of product, there are many extra fields, and they're not the same for each type of product (author for books, list of ac tors for DVDs, ...). And I will keep the ability to create new types of products in my backend at any time. It looks like this:

Product DVD:

- list of actors
- director
- release date in Cinema
- release date in DVD

Product Book:

- author
- collection
- editor

Product CD:

- artist
- genre

I'm using Ubercart as my e-commerce module in Drupal. I also need common fields for every type of product (price, possible discount, ...). I don't want to create my nodes/fields manually every time I change them in the backend, I want them to be replicated automatically via my webservice (I've seen the node API and Ubercart API?).

Second thing, some "products" will not be buyable, they're part of a product and I want to talk about them, but they can't be bought alone (a goodie belongs to a DVD, there is a node describing it, but you can't buy the goodie alone). In my backend, the goodies are the same type of data as my products, but they're flagged as "not buyable". And what if sometimes I want to make some goodies buyable, and some others not?

Thanks in advance for your help.

Kinds regards, Cyril.

⋅ Categories: Drupal 6.x