Enabling/Disabling modules does not clear cache (menu)

I've been experiencing this too, I've become accustomed to running 'drush cc all' now after any 'drush en' command.

Some people are reporting this happening in the Edit module issue queue, too: #1665612: AJAX errors when installed using Drush

I've seen this happen on Views UI as well, afaik. Not sure when it started.

This feels a bit more important than "normal."

Confirmed.

Probably since #1565888: pm-enable and pm-disable throw errors when hidden modules are enabled

In the mentioned issue we removed a call to system_modules_submit() that do a cache clear at the end.

Attached patch calls to drupal_flush_all_caches() and also adds a test.

Perhaps add a comment above the flush lines.

Committed, with comment.

Should be great to also apply it for drush_module_uninstall().

For e.g, i alter an existing entity declared by an another module. I alter schema (using hook_schema_alter), added fields to tables with a hook_install() but also alter the entity info (hook_entity_info_alter).

When we uninstall the module, it will drop fields by implementing a hook_uninstall (which seems to update schema ?) but entity info are not cleared. As a result, when entity api try to load an entity of this type, it used a corrupt base table schema.

If i uninstall this module via UI, i thinks it will call something like drupal_flush_all_cache, which call entity_info_cache_clear() to update entity schema. And no errors occured.

Here a simple patch attached.

Did i make something wrong ?

So in your case it works via web and not with drush?

This is the submit handler for uninstalling modules via web:
http://api.drupal.org/api/drupal/modules%21system%21system.admin.inc/fun...

It doesn't flush caches, or I'm missing something.

You're right. My mistake to think that this error occured on uninstall (it appears when disable the module) and this patch works great !

Thanks and sorry for this mistake

Rock!! Thanks, jonhattan!

@jonhattan, when will the next stable version be released? I think this is quite important.

Thank you very much for the work done :).

I can confirm that when I upgraded from 5.4 to 5.8 this issue was resolved.