Last post Dec 19, 2005 10:16 PM by BKdotNet
Dec 13, 2005 09:34 AM|JudoTom|LINK
So far these forums have been a great help and I have only been reading. I just got started w/ dotnetnuke and so far things are great.
Ive been working on a site and I was trying every module under the sun and most worked great. I have DNN 4.0 and again so far so good. I did make one mistake that I can not seem to correct. I downloaded a module (DMX document manager lite) and I deleted
the module directory. I had thought I had already deleted the module from withind the DNN module definition screen but I did not. Now when I go to delete the module from within DNN I get an error message saying "Invalid
Folder name for Module. Cannot delete Module." Its not a big deal but I was wondering if there is a fix for this?
Perhaps deleting the record from the table or something like that but I was wondering how I might completely remove it.
Dec 13, 2005 11:17 AM|sowens|LINK
Dec 13, 2005 01:01 PM|mikeh36|LINK
It sounds like his problem is with deleting it from the Module Definitions page to me based on the "Can't find folder" message. You can deleted it straight from the database (by memory you need to look in the ModuleDefinitions, Modules, and (maybe) DesktopModules).
You could try recreated the directory under the DesktopModules directory and then deleting the module. That might be just enough to get it to work.
Dec 13, 2005 04:44 PM|JudoTom|LINK
ahh that is pretty sneaky and sounds like it will work.. i hope its not looking for certain files in the directory..
I also noticed another problem. It seems that I can not add anymore modules. Whenever I start the process of adding a new module I select the zip file add it to the box below then click upload file... normally it would scroll throught a list of all the
files added and the changes made and then end with a module installed successfully statement.. now it just jumps right back to the module page..
this is my first run w/ DNN and i might have just 'hosed' things up past the point of no return? Its no big deal and it might have something to do w/ the fact that i have like 30 old/older modules running in 4.0? who knows but if anyone has ideas on how
to fix that a bit it would be great.
i will try the directory trick and let you know if it works!
Dec 13, 2005 05:59 PM|mikeh36|LINK
Dec 14, 2005 09:46 AM|JudoTom|LINK
Thanks again for the help!
I dont get an error message it just goes right back to the module screen that lists all the modules?
I didnt get a chance to try the 'directory' trick just yet but I am going to do that and see if it works.
Is it possible that by installing/deleteing/removing 30-50 modules form 1.0-3.0 into DNN 4.0 that the system is just 'messed up' Right now this is just sitting on my local computer and i have been experimenting w/ tons of different things so if so i would
not be suprised. I obviously wouldve been more careful if this was live or going live but this is just my test project for now.
Dec 16, 2005 06:12 PM|edgett|LINK
This error is a bug in DNN, when a module uses a folder like DesktopModules\MODULEDEVELOPER\MODULENAME instead of DesktopModules\MODULENAME.
Dec 19, 2005 10:16 PM|BKdotNet|LINK
Just as an afterthought - if you have a module which throws an exception, that module can be painfully difficult to remove from DNN without deleting the page or going into the DB and surgically removing the references.
Core Team - Worth looking into this...or at least providing some way to abort a module and remove it automatically if it throws a painful exception which ends page execution.