Just installed Drupal 8 and messed with it for a while. It looks great but I'm having a hard time with modules. My first issue is I have a SUPER-SIMPLE module that simply tries to inject CSS and JavaScript files. I have succeeded with that module --- however, I don't see it in my uninstall list as able to be uninstalled. In the module list, the enable checkbox is grayed out too. My module wrote no tables and has no dependencies, it seems to be unable now to be removed via the front-end.

The second, and bigger issue: Installed Administration Menu for D8 and it broke down my D8. Then I removed the module files and cleared cache but now I'm getting the following red errors:
Notice: Undefined index: admin_devel in Drupal\Core\DrupalKernel->discoverServiceProviders() (line 232 of core/lib/Drupal/Core/DrupalKernel.php).
Notice: Undefined index: admin_menu in Drupal\Core\DrupalKernel->discoverServiceProviders() (line 232 of core/lib/Drupal/Core/DrupalKernel.php).

I see outdated instructions here of how to manually remove modules --- but no info that works in current/latest 8.x-dev that I downloaded a few days ago:
http://drupal.stackexchange.com/questions/72927/manually-disable-module-...

However, in comparing D8 and D7 (using the system table, etc.), it was so much easier to force-disable or remove a module. In D8, I unloaded and searched the entire database and D8 file structure for "admin_menu" and "admin_devel" that you see in the errors above but to no avail.

Any suggestions or fixes would be greatly appreciated!

Comments

krisp1’s picture

krisp1 commented

I have been greeted with a similar error message- Notice: Undefined index: backup_migrate in Drupal\Core\DrupalKernel->discoverServiceProviders() (line 232 of core/lib/Drupal/Core/DrupalKernel.php) after uninstalling D8 backup_migrate module using drush pm-uninstall, clearing all caches, database, ad infinitum. Perhaps some module setting remnants remain in DrupalKernal somewhere? Either way it looks like some more investigation into Symfony services is in order, and it may be time to take my pre-emptive headache medication.

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
commented
Priority: Major » Normal
Issue tags: -D8, -disable module, -remove module, -uninstall module, -bad module

This is not a core bug, you're installing contrib modules that are probably broken.
I have no problem installing/uninstalling working modules.

tr’s picture

tr commented
Status: Active » Postponed (maintainer needs more info)

Is this still an issue with the current version of Drupal 8.0.x-dev?
Uninstallation of modules which errored during install was fixed recently in #2474363: Stuck in failed module install process.
I don't think there's a problem here any more.

Joan_Carles’s picture

Joan_Carles commented

I've got this same error. I'm sorry but I'm not any dev so I don't know how to use git neither drush. So, could you bring some help and let me know how can I revert this module installation? Perhaps manually?
I'm completely stuck with this "fatal error" [Call to undefined function user_access() in /usr/home/www/modules/admin_menu/admin_menu.module on line 149]
This is very frustrating...

Thanks in advance.

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

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.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.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.

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

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.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.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

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

tr’s picture

tr commented
Status: Postponed (maintainer needs more info) » Closed (outdated)

No further information provided, so I assume the OP has resolved the issue. If this is still a problem and you can provide additional information, including steps to reproduce the issue, then feel free to reopen this issue.