In its current implementation, each rule is exported without reference to its "weight" field. As this module's functionality hinges upon the order of rules in the chain, this oversight makes it impossible to revert a site back to a known-good state after misconfiguration.
Also, the Features UI displays an md5 hash of each rule, which makes it difficult to comprehend which rules appear in different modules. It may be preferable to use a machine-readable version of the "string" field already being generated for export as the key for import/export.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 1513070.patch | 27.23 KB | mkalkbrenner |
Comments
Comment #0.0
jpklein commentedEdit for readability
Comment #1
mkalkbrennerIt's a difficult thing to export parts of the chain and import them in another chain using features.
The import might break the existing rule chain
Therefor I postpone this feature until someone comes up with great ideas.
Comment #2
mkalkbrennerI started a reimplementation of the Features integration.
The current one was just a first experiment.
Comment #3
mkalkbrennerThat was hard!
This really requires some more testing. Help is welcome!
Comment #4
mkalkbrennerComment #6
mtunay commentedHas this been pushed to the repo? I cannot find the commit.
Comment #7
mkalkbrennerYes: http://drupalcode.org/project/themekey.git/commit/62b08ba
But there's still an open issue: #1763784: feature recreate seems to broken
Comment #7.0
mkalkbrennerClarified issues