Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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
Comment #1
fagoNot sure what the module does, but exporting conditions works. Please do some more investigation of what goes wrong.
Comment #2
mitchell CreditAttribution: mitchell commentedComment #4
mitchell CreditAttribution: mitchell commentedThat 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.
Comment #5
rszrama CreditAttribution: rszrama commentedfwiw, 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.
Comment #6
pvhee CreditAttribution: pvhee commentedReopening 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?
Comment #7
pvhee CreditAttribution: pvhee commentedForgot to reopen..
Comment #8
rszrama CreditAttribution: rszrama commentedIt 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.
Comment #9
derhasi CreditAttribution: derhasi commentedI 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.