Jeff, as soon as I saw this I started thinking about a content removal add-on for the Util package, using the Batch API. Also, I understand that D7 has fixed this but pre-D7, blocks never went away either (unless, like me, the devloper explicitly did it). Nancy Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
________________________________ From: "j...@ayendesigns.com" <j...@ayendesigns.com> To: development@drupal.org Sent: Wed, January 26, 2011 7:31:41 PM Subject: Re: [development] D6 Cleaning up on module uninstall Good points from you and everyone else. On a tangent to this example, I think about the "completely uninstall" and "lose all data" messages, and that apparently the accepted way of doing it leaves many footprints. Sort of like when I have Windows remove an app and yet there are files and registry entries left all over the place, though in that case I don't think its by design. I don't know if this is also the case in D7, but if so, it might be fodder for a Cleanup module that accepts registration of all a module's pieces and then offers the user a choice between a 'standard' uninstall and a truly full one. > Hi, > > You shouldn't remove the taxonomy on uninstall, as people may be using the >taxonomy you created for another purpose, and what you originally intended. >Just >on the uninstall let the user know that they should be deleted. > > If your module defines the content type Drupal will handle the fact that the >definition is missing, and the admin can clean up all the nodes, and other >definitions. > > Gordon. > >
