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.The top-level admin/commerce menu is for day-to-day content operations. Stores are not it. Most sites will treat them as configuration and define them only when the site is installed.
Comments
Comment #2
bojanz CreditAttribution: bojanz at Centarro commentedComment #4
bojanz CreditAttribution: bojanz at Centarro commentedDone.
Comment #6
bojanz CreditAttribution: bojanz at Centarro commentedI had to revert because this could complicate #2885483: Improve the Commerce configuration UX, need to make a decision there first.
Comment #7
joachim CreditAttribution: joachim as a volunteer commentedI'm not sure about this. I get the idea that stores are something you don't change much, and could be tucked away, but from a developer's POV, it's nice to have content entities in the main menu and config in the submenu.
Comment #8
bojanz CreditAttribution: bojanz at Centarro commented@joachim
Ecosystem-wise we're already not respecting that split, because shipping methods are content entities and they are under config.
It's the same case as stores, where we use content entities simply because we couldn't use config entities (due to machine names and them being limited in number)
Comment #10
bojanz CreditAttribution: bojanz at Centarro commentedRe-committed.