DNN Forums

Ask questions about your website to get help learning DNN and help resolve issues.

Deleting Many Legacy Modules

Sort:
You are not authorized to post a reply.





New Around Here





    Friends, I manage a DNN portal that has numerous legacy modules that are no longer used. I would like to remove them from DNN. 

    I know I can using the delete function on the Extensions page, but doesn't that delete process restart DNN? IF so, that would be a lot of downtime. 

    What would be the best way to handle these deletions while minimizing downtims? Thank you. 

    John 






    Senior Member





      Hello John: 

      You're correct that deleting a module will recycle the website in most instances.  It really depends on the extension. If it has any server-side code, then this will continue to be true.  Which is to say, like 98% of the modules you'd ever run into.  

      There really isn't a great way to do this without also incurring the recycles and related disruptions.  This is because there are a lot of things that occur when you uninstall and delete a module. You can try to get around it and limit the number of recycles, but you're only going to end up with orphaned files and data.  These are the kinds of sites that I often get with a note, "Please help! We can't upgrade DNN anymore!"  

      I'd recommend just going through and deleting the modules one-by-one.  Depending on the number of modules, you may want to do a certain number at a time, and of course during non-peak hours, if you have a choice.  Also, one thing I've found to help in the past is to shut down the website to everyone but myself and then run through the time-consuming stuff.  This helps, because the only requests the website is worried about are coming from you.  (Another way to do the same thing is to shut down the website, run the steps on a staging/UAT/test instance, then restore it over production when you're done.)






      New Around Here





        Thank you, Will. I like your final point, which I hadn't considered: copy production, update the copy and then restore it to prod. Freezing development for a few days would be much better than a long downtime. Much appreciated!

        John 






        Senior Member





          Posted By John Wolf on 1/11/2024 2:02 PM

          Thank you, Will. I like your final point, which I hadn't considered: copy production, update the copy and then restore it to prod. Freezing development for a few days would be much better than a long downtime. Much appreciated!

          John 

          It's always my pleasure! 😎 

           

          You are not authorized to post a reply.

          These Forums are dedicated to the discussion of DNN Platform.

          For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

          1. If you have (suspected) security issues, please DO NOT post them in the forums but instead follow the official DNN security policy
          2. No Advertising. This includes the promotion of commercial and non-commercial products or services which are not directly related to DNN.
          3. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
          4. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
          5. No Flaming or Trolling.
          6. No Profanity, Racism, or Prejudice.
          7. Site Moderators have the final word on approving / removing a thread or post or comment.
          8. English language posting only, please.

          Would you like to help us?

          Awesome! Simply post in the forums using the link below and we'll get you started.

          Get Involved