Add new comment

Hi there J-P, thanks for sharing your insight into the crazy world of Drupal code architecture ;-) I am currently building out an install file on a client's module and getting that uncomfortable feeling you have written about. The install file is taking care of setting up and populating a load of content types (with associated fields), taxonomies, menus and views. I have split the file up using module_load_include and sub-files (my-module.node.inc, my-module.fields.inc, my-module.taxonomy.inc, etc.). This has made the code more manageable but probably at the risk of sane architecture.

Ever had to deal with this or any advice on how you would tackle it?

Thanks, Mike.