Custom Module Classes

Couple questions,

• Do you need the node data or a place in the content tree?
• Do you need to have those 70 different attributes and 14 different 1:N classes in the content tree?
• Do any of those 70 different attributes and 14 different 1:N classes need to be searchable?

I can think of a good way to do this with page types and I can think of a way to do this with a custom module. But if you really need to have the node data behind it, you're better off with custom page types and setting the scopes and parent/child relationships.

If you have some custom code needing to be placed behind the classes, then probably better to use the custom module/classes so you can incorporate it all together.

Brenden,

The car needs node data and a place in the content tree, with SEO features and such. The 14 different classes do not need to be in the content tree. The attributes are searchable but not with site search, the are in a custom grid I have built.

I was going down the same path you suggested, thinking it may just be best to do a hybrid with Global Events for cleanup?

Thoughts?

I like the idea of the global events as long as you're comfortable you're deleting all the respective items/records.

So your custom "Car" page type could still have those other fields or attributes related to it on the Form tab. You could create some custom form controls to write data to those other tables (custom tables, module classes, etc.) Just depends on what you want to do I guess. It would be very similar to how you can add categories or attachments. Just don't make those items available until after they have the main node created.