Hello.

I uninstalled the Blog module BUT parts of it lingers whereby I can't reinstall etc. Here is the message received...

Unable to install Blog, core.entity_form_display.node.blog_post.default, core.entity_view_display.node.blog_post.default, core.entity_view_display.node.blog_post.teaser, field.field.node.blog_post.body, field.field.node.blog_post.field_blog_comments, field.field.node.blog_post.field_blog_tags, field.storage.node.field_blog_comments, field.storage.node.field_blog_tags, node.type.blog_post, views.view.blog already exist in active configuration.

Q1: How to fully delete (preferably not manually)
NOTE: I actually may want to reinstall after.

Thanks!

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

drupert55 created an issue. See original summary.

jsulmar’s picture

After uninstalling the module, I notice that 'blog post' remains present on the list of content types.

Zeshin’s picture

I'm experiencing the same issue. I started modifying the user blog post view when Drupal admin suddenly started acting funny (buttons stopped working), and suddenly visiting my site showed an error message and wouldn't display. I tried deleting the modified view to no avail and instead uninstalled the Blogs module: fortunately my site came back up, but now I can't reinstall the Blogs module because I'm getting this "already exists in active configuration" error.

Update: Learned a few things today and was able to reinstall blog module successfully. If you have drush installed, you can show all the items presently in the active configuration using command drush config-install.

You can see in the list all blog-related items that were not removed during the uninstall (and thus remain in "active configuration"). You can then individually remove them using the drush command config-delete. So for example, the error said that "core.entity_form_display.node.blog_post.default" was still in the active configuration, so I used command drush config-delete core.entity_form_display.node.blog_post.default.

There are alternative methods. You can use drush php and then execute the command Drupal::configFactory()->getEditable('config.item.you.wanna.get.rid.of')->delete(); for each item you wish to delete. You apparently can also use the new "Drupal Console" project, which is a Drupal CLI similar to drush that also has a config:delete command.

After removing all blog items from the active configuration, I was able to enable the blog module again. Hope this helps anyone else facing the same issue.

Znak’s picture

Znak’s picture

Status: Active » Needs review
Carlos Miranda Levy’s picture

Two comments:

If you already uninstalled the module before applying the patch though, you have to manually remove the blog_post content type before you are able to reinstall it.

And I also had to remove the Blog menu entries in the Admin Toolbar menu (https://www.drupal.org/project/admin_toolbar contrib module) from Add Content and Structure/Content Types via devel module.

eit2103’s picture

Still the same problem.

Unable to install Blog, field.storage.node.field_blog_comments, field.storage.node.field_blog_tags already exist in active configuration.

How could I delete these 2 fields manually?

nevergone’s picture

Please test 3.x version and write feedback.

paintingguy’s picture

I am experiencing this as well. I have version composer require 'drupal/blog:^3.0' but it will not uninstall completely and I cannot install it as well. Please help. Thank you.

nevergone’s picture

Assigned: Unassigned » nevergone
drush en -y blog; drush cr; drush pmu -y blog; drush cr; drush en -y blog
>  [warning] No configuration objects have been updated.
>  [notice] Message: No configuration objects have been updated.
> 
 [success] Successfully enabled: blog
 [success] Cache rebuild complete.
 [success] Successfully uninstalled: blog
 [success] Cache rebuild complete.

In PreExistingConfigException.php line 65:
                                                                                                                                                                                             
  Configuration objects (core.entity_form_display.node.blog_post.default, core.entity_view_display.node.blog_post.default, core.entity_view_display.node.blog_post.teaser, field.field.node  
  .blog_post.body, field.field.node.blog_post.field_blog_comments, field.field.node.blog_post.field_blog_tags, field.storage.node.field_blog_comments, field.storage.node.field_blog_tags,   
  node.type.blog_post, views.view.blog) provided by blog already exist in active configuration
nevergone’s picture

Unable to install Blog, core.entity_form_display.node.blog_post.default, core.entity_view_display.node.blog_post.default, core.entity_view_display.node.blog_post.teaser, field.field.node.blog_post.body, field.field.node.blog_post.field_blog_comments, field.field.node.blog_post.field_blog_tags, field.storage.node.field_blog_comments, field.storage.node.field_blog_tags, node.type.blog_post, views.view.blog already exist in active configuration.

  • cdda413 committed on 2780203-uninstalling-module-is
    Issue #2780203: enforced configuration items
    
  • a374c75 committed on 2780203-uninstalling-module-is
    Issue #2780203: update existing configuration items
    
  • 24673f2 committed on 2780203-uninstalling-module-is
    Issue #2780203: Add module reinstall test.
    

  • 24673f2 committed on 3.x
    Issue #2780203: Add module reinstall test.
    
  • a374c75 committed on 3.x
    Issue #2780203: update existing configuration items
    
  • cdda413 committed on 3.x
    Issue #2780203: enforced configuration items
    
nevergone’s picture

Status: Needs review » Fixed

Please run database update.

  • 5e11ca5 committed on 2780203-uninstalling-module-is
    Issue #2780203: re-exported configurations
    
  • 927b0b0 committed on 2780203-uninstalling-module-is
    Issue #2780203: update config-update hook
    

  • 5e11ca5 committed on 3.x
    Issue #2780203: re-exported configurations
    
  • 927b0b0 committed on 3.x
    Issue #2780203: update config-update hook
    
nevergone’s picture

Version: 8.x-2.x-dev » 3.0.1
nevergone’s picture

nevergone’s picture

IMPORTANT:

If you have previously uninstall this module and cannot reinstall it, you must do the following:

IMPORTANT:

If you have previously uninstall this module and cannot reinstall it, you must do the following:

  1. Backup the fully site database.
  2. Download and extract Blog module 3.0.1 version.
  3. Rename the config/install directory inside the module: config/optional
  4. Enable blog module
  5. Delete the old module module, and download, extract Blog module 3.1.1
  6. Run database update: update.php
  7. Uninstall the Blog module.
  8. Install the Blog module again.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

Jawahar Balachandran’s picture

We need assistance in installing the Drupal 9.1.0 version in RHEL 8 EC2 instance.

We are not getting installation page.
Drupal and DB configuration
Please assist

dpi’s picture

Issue tags: -uninstall reinstall

Tag cleanup