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!
Comment | File | Size | Author |
---|---|---|---|
#4 | uninstalling_module_is_not_completely-2780203-4.patch | 1.12 KB | Znak |
Comments
Comment #2
jsulmar CreditAttribution: jsulmar commentedAfter uninstalling the module, I notice that 'blog post' remains present on the list of content types.
Comment #3
Zeshin CreditAttribution: Zeshin commentedI'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 commandDrupal::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 aconfig: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.
Comment #4
Znak CreditAttribution: Znak commentedPatch for fixed this problem. Please, check up.
Comment #5
Znak CreditAttribution: Znak commentedComment #6
Carlos Miranda Levy CreditAttribution: Carlos Miranda Levy as a volunteer commentedTwo 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.
Comment #7
eit2103 CreditAttribution: eit2103 commentedStill the same problem.
How could I delete these 2 fields manually?
Comment #8
nevergone CreditAttribution: nevergone commentedPlease test 3.x version and write feedback.
Comment #9
paintingguy CreditAttribution: paintingguy commentedI 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.
Comment #10
nevergone CreditAttribution: nevergone commentedComment #11
nevergone CreditAttribution: nevergone commentedComment #14
nevergone CreditAttribution: nevergone as a volunteer commentedPlease run database update.
Comment #17
nevergone CreditAttribution: nevergone as a volunteer commentedComment #18
nevergone CreditAttribution: nevergone as a volunteer commentedComment #19
nevergone CreditAttribution: nevergone as a volunteer commentedIMPORTANT:
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:
config/install
directory inside the module:config/optional
update.php
Comment #21
Jawahar Balachandran CreditAttribution: Jawahar Balachandran commentedWe 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
Comment #22
dpiTag cleanup