RE: http://drupalcode.org/project/uuid_features.git/commit/b7504e4
Although the feature is nice to have, there are use cases where we do not want UUID Features to force us to export terms along with vocabularies.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | uuid_features-term-export-option-variable-1962782-2.patch | 1.57 KB | saltednut |
| #1 | uuid_features-term-export-option-variable-1962782-1.patch | 1.52 KB | saltednut |
Comments
Comment #1
saltednutHere is a patch that introduces a new variable and turns this feature off by default. There are many cases where people would not be using uuid_term exports but still exporting a vocabulary. Just because the uuid_features module is enabled, it shouldn't imply that we want to do this by default. Its a nice thing to have if you want to turn it on, but there are sites with hundreds of thousands of taxonomy terms that would not want this. By making it turned off by default, it prevents sites from lots of unnecessary cleanup when building features.
Again: nice to have but not so nice as a default!
Comment #2
saltednutThe last patch did not retain default settings from the set variable. My bad.
Comment #3
saltednutAssigning this to myself. Please do not post additional patches. Code review welcome!
Comment #4
duaelfrRTBC for me
I used your patch as a base for mine : #1964722: Notice: Array to string conversion in DrupalDefaultEntityController->cacheGet() (line 369 of includes/entity.inc)
Comment #5
saltednuthttp://drupalcode.org/project/uuid_features.git/commit/789b7bc
Comment #6
saltednut