By -ds- on

Hi there,

I have a Content Type with a lot of fields that are all dependent on each other (fieldgroups are hidden and/or shown depending on selections made, other form elements become 'required' and 'ticked' when certain boxes are checked, entered values are cleared / made unrequired when other form elements are then unselected and so forth ...).

It's quite a massive form in total with well over 160 different form elements (text fields, tick boxes, selection menues, term references and so forth) to it.

To precisely incorporate the required functionality I think it may be wiser to rewrite the content type as a custom module. I have written a few easy content type modules and custom field modules before, but this scale means it is a whole new challenge.

If I could just export the content type and convert it to a module!

I know it's supposed to be possible with Features according to this incomplete post. However, exporting my Content Type using features only gives me an empty .module file and does not include my entire Taxonomy values, but merely the top level. =/

I have also tried ctools - Bulk Export which gives me a 'bundle':

$data = array(
  'bundles' => array(
    'entry' => (object) array(
       ...

and also errors:

Notice: Undefined variable: output in ctools_var_export() (line 837 of /sites/all/modules/ctools/includes/export.inc).

and lastly I tried Bundle Copy, also without any real success....

So, my question is simply this:

How do I best go about the above? The functionality is currently not possible with modules alone ( Conditional Fields for example does not work across field groups - which are necessary to categorise the huge amount of fields on the form page)

Can anyone give me any tips on how to go about creating this module, please?

⋅ Categories: Drupal 7.x

Comments

mgifford’s picture

mgifford
he/him
Primary language English
commented

There's a related link here - http://drupal.org/node/1341082

Don't think that resolves the problem however.

WorldFallz’s picture

WorldFallz commented

just a word of advice....

I had a single content type like this, and ended up having to rearchitect it completely because it was just too many fields-- and this was on d6 when I could set it up so that many fields were all in the same table (with d7 every field is always in its own table).

I split the fieldgroups into different content types, used nodereferences, nodereference_url, nodereference_views, views, and viewfield to tie everything together into one parent content type. I also used quicktabs to add ajax tabs to be able to load stuff on demand.

frank ralf’s picture

frank ralf commented

I got the same error message as in the OP when exporting a custom content type from D 7.12. However, the export data was created and import worked ok.