Problem/Motivation

Currently, it is impossible to export taxonomy.settings.yml.
When for some reason, taxonomy.settings.yml is not part of the configuration export, it is no longer possible to add it.

I think the expected behavior is for it to fall back to the default config?

This results in a bad configured taxonomy after importing configurations.

Proposed resolution/Remaining tasks

Add taxonomy.settings.yml to the configuration export.

maintain_index_table: true
override_selector: false
terms_per_page_admin: 100

User interface changes

None

API changes

None

Data model changes

None

CommentFileSizeAuthor
Schermafbeelding 2016-05-01 om 10.03.09.png28.4 KBharings_rob
Schermafbeelding 2016-05-01 om 10.02.52.png14.92 KBharings_rob
Schermafbeelding 2016-05-01 om 10.02.43.png10.25 KBharings_rob
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

harings_rob created an issue. See original summary.

harings_rob’s picture

harings_rob CreditAttribution: harings_rob at Harings.be commented
Issue summary: View changes
markdorison’s picture

markdorison
he/him
CreditAttribution: markdorison at Chromatic commented
Version: 8.1.0 » 8.1.x-dev
Status: Needs work » Active

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Berdir’s picture

Berdir
Primary language German
Location Switzerland
CreditAttribution: Berdir at MD Systems GmbH commented
Status: Active » Closed (cannot reproduce)

I don't understand this issue. Simple configuration is imported on module install, and exists unless someone would manually remove/delete it. We don't support this for any other simple config, your site would also break without system.site for example.