Hi there

Very usefull module, just one note regarding usability.

I have just spent an hour trying to figure out why my site doesn’t show any nodes any more.

After a while a realized that it’s because I forgot to disable the taxonomy_access module before I uninstalled it.

Is there some reason why module isn’t disabled automatically when it’s uninstalled? That would be more user friendly me think :)

Comments

keve’s picture

keve commented
Status: Active » Closed (won't fix)

You are right. But it cannot be done, since the module is not 'notified' when it is disabled. (But this is the same case, w/ all access type modules).

Ask core developers to make a hook which is called when module is uninstalled. (e.g hook_uninstall).Make a feature request about it on drupal core, then it can be decided to include it later. (I have heard about request for this hook on some of the developers mailinglist)

Until then, you have to read the README.txt better.

keve’s picture

keve commented
Title: Non user friendly uninstall » Hook for uninstall: Non user friendly uninstall
Status: Closed (won't fix) » Active

There is a discussion going on about a hook lfor disable/uninstall a module: like hook_uninstall...

http://drupal.org/node/46422
http://drupal.org/node/45831

(Hook_install was commited to head, but not documented yet).

mi5ha’s picture

mi5ha commented

I see, just wanted to give you Drupal novice pespective. It seems that it will be implemented eventually. Thanx for remark that it’s a common problem for all access privileges modules, that’s usefully related.

I suspected that this question holds a special place in your heart … Hope they’ll patch the core soon so you don’t get an arrithmia :-)

keve’s picture

keve commented
Version: 4.7.x-1.x-dev » master
Status: Active » Fixed

Hook_unintall is commited to HEAD (will be available for 5.x)

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)