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.

CommentFileSizeAuthor
#3 1513070.patch27.23 KBmkalkbrenner

Comments

jpklein’s picture

Issue summary: View changes

Edit for readability

mkalkbrenner’s picture

Status: Active » Postponed

It'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.

mkalkbrenner’s picture

Title: CTools exportables and Features support » Improve Features support
Version: 7.x-2.0 » 7.x-2.x-dev
Assigned: Unassigned » mkalkbrenner
Category: feature » task
Status: Postponed » Active

I started a reimplementation of the Features integration.
The current one was just a first experiment.

mkalkbrenner’s picture

Status: Active » Needs review
StatusFileSize
new27.23 KB

That was hard!

This really requires some more testing. Help is welcome!

mkalkbrenner’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

mtunay’s picture

Has this been pushed to the repo? I cannot find the commit.

mkalkbrenner’s picture

mkalkbrenner’s picture

Issue summary: View changes

Clarified issues