Support for export filtering via Drush

Created on 2 March 2017, over 7 years ago
Updated 27 January 2024, 5 months ago

This issue is not really *fixed* rather 2.x is deprecated and it is marked as fixed in order to give credits to people participating and moving it forward.

In #2846026: Support for export filtering → has been discussed to confirm that module does not filter configuration export.

But, I would see this feature very useful and according to module name, I see this module to be the best place to support this functionality as my use case is about ignoring configuration export (too).

Is there any blockers or thoughts, why this feature should NOT be part of the module? And what is the best approach to start with?

A similar feature is under TBD for version 3 in ✨ Allow to configure different behaviors. Fixed .

✨ Feature request
Status

Fixed

Version

2.0

Component

Code

Created by

🇫🇮Finland iMiksu Finland

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇧🇪Belgium LOBsTerr

    Thank you for such a useful feature, it is very helpful and should be included in this module.
    I have tested, for me it works perfectly

  • 🇧🇪Belgium Fernly

    If anyone says "thank you, it works", please also mention what patch you used on which version. Thanks!

  • 🇺🇸United States JonMcL Brooklyn, NY

    Patch does not apply to the 8.x-3.0 branch. The enable_export_filtering setting is now part of the module's schema, but it is set to false by default. I also can't find anywhere it is used and no way to change it on the settings form.

    Any chance some of the maintainers could chime in? Maybe the setting was added in anticipation of a new release?

  • 🇨🇭Switzerland bircher 🇨🇿

    This issue is for 2.x in 3.x this has been implemented from the first tag on the branch. On the contrary one could not turn it off until 3.0

    But now that 3.0 is released you should just update to it. If you want this patch then just updating will be enough, if you don't want it you switch to intermediate mode and clear out the export list.

  • 🇺🇸United States JonMcL Brooklyn, NY

    @bircher My mistake and please accept my apologies if my question seemed like a complaint.

    I searched for the this patch's config property and I thought I saw it in the 3.0 module's schema file, and then no references to the property in the code. However, I was incorrect and the enable_export_filtering property is not used or needed.

    The 3.0 version of the module is working great, for both import and export, in simple mode. Thank you!!

  • Status changed to Fixed 6 months ago
  • 🇨🇭Switzerland bircher 🇨🇿

    I am marking this fixed in order to give everyone who contributed to this issue credits.
    The 2.x branch for which this issue is will not get any further commits. And the 3.x branch now has this feature.

    But a lot of patient people cared about this issue and I want to acknowledge their efforts. The only way to do this is according to the maintainer documentation → is to mark the issue as fixed.

    So thank you all for working on it and please upgrade to the latest 3.x release. YOur config is backwards compatible but please run the update hook as it will add a new setting where you can choose "intermediate" if you do not want this feature turned on by default (which is what the simple mode will do) (But do so via the UI the config schema is different for intermediate or advanced modes)

  • 🇨🇭Switzerland bircher 🇨🇿
  • 🇨🇭Switzerland bircher 🇨🇿
  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.69.0 2024