I enabled maxlength so one of my fields could benefit from its use. All of the sudden, all of my features have maxlength settings injected into them when I re-export. IMHO this is a major issue, this module is essentially unusable for major sites where they expect clean settings exports.
Shouldn't it work like this:
1) On edit form, user sees ability to enable the maxlength module for this text area
1a) if that checkbox not checked, no processing is done on that field
2) user checks box, only after that are maxlength hooks added to that field
Comments
Comment #1
joelcollinsdc commentedFor example, this is the diff of a content type (that i didn't enable maxlength on at all)
Comment #1.0
joelcollinsdc commentedbeing less of a jerk
Comment #2
slv_ commentedPatch attached. That should fix the issue.
Comment #3
joelcollinsdc commentedThanks!
Comment #4
lpalgarvio commentedhow is this coming along?
Comment #5
lpalgarvio commentedI've tested it and it works fine. May be ready for commit and roll out on new release
Comment #6
lpalgarvio commentedstill no issues so far. please commit
Comment #7
b-prod commentedPatch in #2 fixes the issue, commit would be welcome.
Comment #9
frjo commented