I don’t see any way to do this at present (and don’t desperately need it), but I can imagine situations where developers might want the user’s input to determine what to do during the uninstall.
Unless this is there already, we might want to consider the option of having a second user input html file that would show in the uninstall before any php resolvers execute and pass options to them.
I create some resources in both EZfaq and SPForm with a script resolver that I can’t uninstall because the user may have changed the fields I could use to find them. I currently just put a message in the console during the uninstall telling the user that they’ll have to be removed manually, but I could theoretically ask the user for their doc ids during the uninstall. Even if I could find them, I wouldn’t want to wipe out the user’s FAQ content without asking.
BTW, how *do* we remove objects in a script? Is there an $object->delete()?
Quote from: splittingred at Dec 12, 2008, 09:08 AM
A good idea might be having 3 options:
- install-options - This would replace the current ’setup-options’.
- uninstall-options - These would show on uninstall.
- upgrade-options - These would show on upgrades only.
I can definitely see uses for all three. I suppose reinstall-options would be overkill.
I wonder if there are any advantages to doing it with a single php file like a script resolver with a case statement and let users echo or return the HTML.
