Go to previous topic
Go to next topic
Last Post 29 May 2013 01:13 PM by  Steve L
Does not uninstall correctly, site crashes after ninstall
 7 Replies
Author Messages


New Member


Posts:
New Member


--
28 May 2013 09:09 AM

    When I tried to uninstall the module, it did not remove the cleanup schedule, my site crashed after the uninstall.

    Suggestion: provide a pre-uninstall option for the host so that the schedule is removed & the Default.browser file is deleted. Note: In general we do not give FTP access to sites (security measure), so deleting files from the website file system other than the portals subfolder is not possible.

    0


    Veteran Member


    Posts:2956
    Veteran Member


    --
    28 May 2013 12:10 PM

    Hi,

    Please follow the Uninstall steps described here. The Optimizer works on low level ASP.NET file and should be removed by the system administrator. In the future, we'll review if there's a better way to remove the file (the DNN manifest has limited ability when it comes to uninstalling).

    0


    New Member


    Posts:
    New Member


    --
    28 May 2013 02:04 PM

    "Encourage us so we keep making great software!"

    I do.

    Please make a decent pre-uninstall routine in the module accessible to the Host where website file and folder access is unnecessary (and I am fully aware of the limitation of the DNN install manifest and uninstall options). The current need to access the file system can be lifted by such a simple option in the module.

    In minimum, there sould be a notice/text explaining the uninstall process in the module itself. The need to go back to the website to read the uninstall instrictions will not work in the long term, since there is no notice whatsover that there is a special instruction for the uninstall.

    0


    Veteran Member


    Posts:2956
    Veteran Member


    --
    28 May 2013 06:30 PM

    Thank you for the suggestion. All our products uninstall cleanly except for the Optimizer, which requires intervention to remove a single file because of the the limitation in the DNN manifest to remove a low-level system file. I'll ask DNN Corp. if there's a way they can enhance their manifest to do more complex clean up.

    0


    New Member


    Posts:
    New Member


    --
    28 May 2013 06:46 PM

    Your answer completely bypasses my suggestions and a way to provide a solution yourself.

    Isn't it your module that requires an special uninstall and your choice to do (or not do) anything about that?

    NB No pun intended, I am just looking for great software and your module seems to solve a case.

    0


    Veteran Member


    Posts:2956
    Veteran Member


    --
    28 May 2013 07:59 PM

    I think you misunderstood. I acknowledged your suggestion by replying with "Thank you for the suggestion". I then said we need to speak with DNN Corp. first and see if there's something we can do with the manifest itself. If we can uninstall cleanly by the manifest, the extra message won't be needed at all.

    In either case, for any module, we always encourage the users to do their due diligence and read through the Users manual before doing any kind of installation. The Users manual talks about installation requirements, how it works and how to uninstall. These are all equally important topics that a user should be aware.

    0


    New Member


    Posts:
    New Member


    --
    28 May 2013 09:48 PM

    Well, it might be that my native language <> English, so explaining, writing and understanding English create a barrier.

    All details about the install manifest can be found in the DNN Wiki:

    http://www.dotnetnuke.com...es/cat/Manifest.aspx

    There is no such thing as an UnInstall interface, like the iUpgradeable interface you have implemented to be used during installation.

    As for RTFM: please understand that there might be a gap in time as well as person between the moment of installation and the moment of uninstall. A simple text explaining what to do would help (and prevent).

    As for language: a suggestion (request): please implement the standard DNN localization. It would make the module more in line with common DNN module development standards and usable for others not speaking English (and there are a lot of countries that don't).
    If you feel unfamiliar or uncomfortable with lcoalization, please ask. We might be of assistance.

    0


    Veteran Member


    Posts:2956
    Veteran Member


    --
    29 May 2013 01:13 PM

    No problem, I just want to make sure you don't feel we push aside your feedback. We already started inquiring about what better ways to uninstall. As you noted, there is no IUninstall interface, only IUpgradeable. We have pushed to put in a feature enhancement to DNN for it.

    We will add to our future todo to localize the Optimizer and we understand the importance of it. Our Revindex Storefront software, for example, is already partially localized for 5 languages and we recently assisted in a DNN Corp. sponsored localization tool that is now available to community for download on Codeplex.

    Thanks,

    0


    ---