Last post Sep 22, 2005 02:55 AM by sydneyman007
Sep 20, 2005 01:31 AM|sydneyman007|LINK
Sep 20, 2005 08:23 AM|jjohns09|LINK
Let me first say welcome to the DotNetNuke community. I am sure that you will find it as valuable as I have.
To answer your question, I was first going to suggest the you look through the
Guided Tour on the DotNetNuke website. However, after looking at it, I soon discovered that it doesn't really cover this very fundamental topic but it is a good read nonetheless.
If you downloaded a module from an external resource hopefully it came in the form of a zip file. This zip file should contain files with extensions like .dnn (custommodule.dnn) which contains a manifest of what is being installed. The installer uses this file
to know what files should be installed and where they should be saved. Your zip file should also contain any number of .ascx files. For instance, one acting as the view module when the module is loaded. It might contain a settings.ascx which is used to view/change
module settings usually how something should appear. It might also contain an edit.ascx file for modifying or adding content to the module. If the module accesses the database, you will probably also see .SqlDataProvider files that create tables and stored
procedures used by the module. And, of course, you will also see one or more .dll files that contain all of the module code.
So, let's see how this relates to an actual download. Let's take the custom links module from my website
BestModules.com. You will have to register first, but the module is free. The downloaded zip file is named BestModulesLinks.zip and contains the following files;
To install this module after download:
Login as Host
Host Menu >> Module Definitions
Upload New Module (Either from the Actions Menu or Link at the bottom of the screen)
Browse and select the BestModulesLinks.zip
Click 'Upload New File'
From here, the DotNetNuke PA installer will run and hopefully will do os without any errors. Once completed, click 'Return'. You should now have the BestModules -Links module available in modules dropdown within the control panel.
You should be able to apply this information to any module that you download, and I hope you find it useful. It's probably more than you wanted to know, or perhaps less.
Sep 20, 2005 09:34 PM|sydneyman007|LINK
Sep 21, 2005 08:43 AM|jjohns09|LINK
You shouldn't need to FTP the files. This really defeats the purpose of the DotNetNuke PA installer. However, maybe the issues lies with your webhost and the placing of the .dll files in the root bin directory. All issue that I have experienced have been
immediatley recognizable in the installer by alerting me to the errors in red. What you are talking about is manually creating the module definition pointing to the uploaded files. Here again, I will use my custom Links module as reference because it is what
I hope that this all made sense. One thing that I am not is a teacher. They require too much patience. You're module might be simpler if it doesn't need to access the database, you can skip that step. All of this has certainly given me food for thought.
I will be releasing another module later today that does store anything in the database. I might want to include some material on both an automated install and a manul install.
Sep 21, 2005 08:59 AM|leupold|LINK
Sep 22, 2005 02:55 AM|sydneyman007|LINK