A suggestion for a patch to have the settings on the node form available as a ctools content type - patch in next post.

CommentFileSizeAuthor
#6 content_type-1955414-6.patch5.53 KBMiSc
#1 content_type-1955414-1.patch3.75 KBMiSc
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

MiSc’s picture

MiSc CreditAttribution: MiSc commented
FileSize
content_type-1955414-1.patch3.75 KB

Patch attached :-)

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna commented
Status: Active » Needs work

Is there a reason to have the 'hide advanced' option?

MiSc’s picture

MiSc CreditAttribution: MiSc commented
Status: Needs work » Needs review

Yes, if you want to not want the advanced settings, which I did not in my project.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna commented
Status: Needs review » Needs work

If any of the submodules are enabled might you not also want to hide those? I suggest rewriting it to see what fieldsets are included and then provide options to hide each one.

MiSc’s picture

MiSc CreditAttribution: MiSc commented

Good point, I will work on that.

MiSc’s picture

MiSc CreditAttribution: MiSc commented
FileSize
content_type-1955414-6.patch5.53 KB

Reworked the patch, now checking for submodules also.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna commented

This needs further work to handle the optional fieldsets dynamically rather than them being hardcoded, that way it won't have to be updated as we add more submodules.

MiSc’s picture

MiSc CreditAttribution: MiSc commented

I am all in for suggestions - I have problem seeing how to do it dynamically, so point me in the direction :-)

MiSc’s picture

MiSc CreditAttribution: MiSc commented

I think, if this should be dynamic, we need to add stuff to the submodules, to identify them as submodules, I will try to do a patch on that later this week.