When exporting a node type as part of a Feature, http://drupal.org/project/features, it would be nice if the Node Form Settings was exported automatically as well. Fortunately its very easy to accomplish this - I'm attaching a patch that adds this functionality.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | patch-nodeformsettings-features-3.patch | 2.37 KB | lelizondo |
| #3 | nodeformsettings_features_2.patch | 1.36 KB | voxpelli |
| #2 | nodeformsettings_features_2.patch | 1.34 KB | voxpelli |
| nodeformsettings_features.patch | 877 bytes | voxpelli |
Comments
Comment #1
lelizondo commentedThanks, works great, I just added the comment variables. http://drupal.org/cvs?commit=503420
Comment #2
voxpelli commentedThere seems to be a shortcoming in my original patch - making it sometimes export the variables when they shouldn't be exported. here's a follow up patch.
Comment #3
voxpelli commentedThere was a typo in the previous patch - fixed in this one.
Comment #4
lelizondo commentedExactly what was wrong? I implemented this on 6.x-2.x. 6.x-1.x is frozen.
Comment #5
voxpelli commentedIt exported the variables on all features dependent on the node type - not only the feature exporting the node type - and it also exported the variables no matter if they had been exported in another feature or not. See #1078478: Multiple features and strongarm conflicts and #904558: Multiple features and strongarm conflicts for related issues.
Comment #6
lelizondo commentedWell, then I should rewrite the patch, the reason for this is because 6.x-2.x has been rewritten and now instead of several variables, it only uses one for each content type and module (Comment Form Settings has been separated into its own module).
Comment #7
lelizondo commentedI've just remade the patch for 6.x-2.x based on your patch. Can you please test?
I also pushed a new branch "features" with the patch applied http://drupal.org/node/582610/git-instructions/features/nonmaintainer
Comment #9
kssundar commentedPorted to 6.x-3.x