Removing the acquia_subscription_status menu


For a Drupal site I was developing I originally tried out the Acquia distribution but ultimately dropped it in favor of the vanilla core release. In doing so I also removed the custom Acquia modules that provided integration with their network as I wasn't going to be using it either. All was good, except that the admin menus retained an unneeded menu item named "acquia_subscription_status" that just linked to - I had to vanquish it!

Having removed all of the custom Acquia modules I was confused as to why there was this random menu item hanging around. It wasn't part of any of the contrib modules I was using, so I grep'ed my entire site to see if something remained - it was clean. Given the admin_menu module works off the normal menus I then tried the configured menus, again to no avail. So that just left the database.

In the database it seemed fairly obvious that it should be in the menu tables, and sure enough it was. The menu_links table included a menu item that went something like this:

menu_name: admin_menu
link_title: acquia_subscription_status
external: 1

Sure enough, this was it. So then I just removed the menu item and..

It was still there. :-|

A quick look identified the simple fact that the menu was cached! Duh.

So, a quick "TRUNCATE cache_menu;" (or Flush All Caches -> Menu) later and life was good, the menu item was gone.


Damien, you are one of the

Damien, you are one of the only guys at our local Drupal user's group who would ever:

A) go digging in the database for an errant menu item
B) use a TRUNCATE command to clear the cache, when admin_menu has a button that will do it for you

I'm just saying - glad you're part of the community. :)

That was really interesting –

That was really interesting – it must have been really confusing to have seen that random menu in spite of removing all the custom Acquia modules and I am sure that it required a lot of effort and patience to find out what the problem was in the end!! This is sure to help a lot of developers to get rid of such problems and check out the database to really get to the root of the problem!!angies list

How to reply

Care to add your own 2 cents? Let me know via Twitter or my contact page.