Commerce Flat rate shipping is a module difined inactive rule. It was edited and activated. When I clone or export, only the unchanged event trigger and the changed action are copied, not the condition. Is that a problem of the Flat rate module or is that an issue of the rules module?

Comments

fago’s picture

Status:Active» Postponed (maintainer needs more info)

Not sure what the module does, but exporting conditions works. Please do some more investigation of what goes wrong.

mitchell’s picture

Project:Rules» Commerce Flat Rate
Version:7.x-2.0» 7.x-1.0-beta1
Component:Rules Engine» Code
Status:Postponed (maintainer needs more info)» Fixed

Status:Fixed» Closed (fixed)

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

mitchell’s picture

Version:7.x-1.0-beta1» 7.x-1.x-dev
Status:Closed (fixed)» Postponed (maintainer needs more info)

That looks like a complete accident that I marked it fixed.

> Is that a problem of the Flat rate module or is that an issue of the rules module?
This issue is not an issue with Rules directly, but it's still a Rules implementation. The things you mention are most likely issues with the code in this project.

> Commerce Flat rate shipping is a module difined inactive rule.
I looked for the git repo for a default rule and didn't see it. Could you please point to the code that creates the rule?

> It was edited and activated.
Please post this export too.

rszrama’s picture

Title:Exporting /cloning rule does not include conditions» Allow default rules configuration to be overridden.
Category:bug» feature
Status:Postponed (maintainer needs more info)» Closed (duplicate)

fwiw, in Commerce Shipping 2.0 we implemented hook_module_implements_alter() to ensure our default Rules configurations are defined before any other module's. This means your module that exports a Rule will now be able to override the default configuration from the Shipping module.

pvhee’s picture

Reopening this issue, as exporting components defined by a particular flat rate service do not seem to be exportable. Any idea on how to export these settings?

pvhee’s picture

Status:Closed (duplicate)» Active

Forgot to reopen..

rszrama’s picture

Status:Active» Closed (duplicate)

It would take some sort of Rules / Features integration; I'm not sure what folks normally do for that, but I'd go look around for that sort of module.

derhasi’s picture

I wrote a helper module two days ago to support moving default components to features, it is a sandbox called "disable defaults": http://drupal.org/sandbox/derhasi/2004516

This should work fine for all components using "module_implements". For ctools based plugins there may be some more lines to register the missing APIs, currently there is only views_api supported.