Configuration Export

Created on 5 January 2023, almost 2 years ago
Updated 20 September 2023, about 1 year ago

The module does not export its configuration.

Steps to reproduce

  1. Create a new shipping method at : /admin/commerce/shipping-methods/add
  2. drush config export
  3. Check the contents of the configuration and you will see that the data you put there is not there
🐛 Bug report
Status

Fixed

Version

2.0

Component

Code

Created by

🇮🇹Italy uccio Turin

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

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

  • Hello,
    I am facing issue releated to this missing feature. I have my payment method depended on shipping type (Cash on delivery on courier delivery). Payment method is part of configuration so it's exported. The is also exported dependency on shpping method as ID.
    But on my production website has shipping method differend ID so it's not mapped.

    What is adviced approach how to handle this?

  • 🇮🇹Italy finex

    Hi, I'm on the same situation. Please, would be possible to provide a robust solution to fix this issue?

  • 🇮🇱Israel jsacksick

    A robust solution to fix what issue? Shipping methods are content entities, like stores, products etc... So a solution to fix what issue exactly?

  • 🇮🇹Italy uccio Turin

    @jsacksick we understood that the module uses "content entity" and not "config entity" however all the rest of commerce exports and imports its configurations and makes it possible to version the ecommerce.

    Would it be possible to think about converting the approach and having config entities?

  • 🇮🇹Italy finex

    @jsacksick see comment #4. It looks a bug to me. Why a payment should be a config and a shipping an entity? What's the logic?

  • 🇮🇱Israel jsacksick

    They're both entities, payments are config entities, while shipping methods are content entities. That was a design decision made years ago... (So not really something we can change at this point). Config entities aren't really scalable after a certain amount. Choosing content entities over config entities for shipping methods was made to allow complex usecases for marketplaces etc. You could use a module like "default_content" for example to export your shipping methods and import them on install or something...

Production build 0.71.5 2024