Problem/Motivation

In earlier versions of Drupal you could just delete a module from the file system and clear caches and stuff would work. In Drupal 8 if you do this it becomes impossible to import configuration because we validate config before import.

Step to reproduce:

  1. Install a module
  2. Remove the module code
  3. Try doing in single config import

You won't be able to because it will produce an error saying:

Proposed resolution

Decide what to do when a module goes missing. One option could be add a message to the status report telling the user a module is missing and that they should put it back and uninstall it.

Remaining tasks

User interface changes

API changes

Data model changes

Files: 
CommentFileSizeAuthor
Screen Shot 2016-05-12 at 16.34.47.png44.57 KBalexpott

Comments

alexpott created an issue. See original summary.

alexpott’s picture

Issue summary: View changes
Issue tags: +Configuration system

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

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now 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.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now 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.

juanjesustrigo’s picture

Assigned: Unassigned » juanjesustrigo

I'll work on this.