Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Import of custom module blockedImport of custom module blocked
Previous
 
Next
New Post
10/14/2012 12:24 PM
 

I am trying to move a custom module from one server to another. The export runs without error. When I import (via Install Extension Wizard) I point to the .zip file and then see the following message:

     If you have reached this page it is because the installer needs to gather some more information, before proceeding.

However, the Next button does nothing (it is not grayed out, by the way). There are no errors or other indications of any problems and there is no prompt for any further information on the screen.

So, I am completely blocked here. Any ideas on how I might resolve this? I am using DNN 6.0.1.

Thanks.

Mark

 

 
New Post
10/14/2012 2:55 PM
 
Please check if the module.zip file have a dnn file (Manifest file) included and check if all needed files included in the Manifest file.
 
New Post
10/14/2012 3:01 PM
 
Matthias Schlomann wrote:
Please check if the module.zip file have a dnn file (Manifest file) included and check if all needed files included in the Manifest file.

Thank you for the response, Matthias. Yes, as far as I can tell the .zip file has everything it needs. The structure I see within the .zip file is.

     App_LocalResources

              view.asc.resx

     Documentation

            (three standard files here in here)

     _<modulename>.dnn

     View.ascx

     View.ascx.db

That all seems accurate to me, right?

Thanks again.

Mark

 
New Post
10/14/2012 4:19 PM
 
I am not sure at 100% about I always create my packages with VS and MS Build. For me it Looks as a not compiled module, and there have to add a Line into the web.config file then. This could be done with the Manifest file. A compiled module have also a dll file into the bin Folder of your DNN instance.

The error message told me that anything is missed on the Manifest file, so you should check the Content of the Manifest file.
 
New Post
10/15/2012 4:15 PM
 
Matthias Schlomann wrote:
I am not sure at 100% about I always create my packages with VS and MS Build. For me it Looks as a not compiled module, and there have to add a Line into the web.config file then. This could be done with the Manifest file. A compiled module have also a dll file into the bin Folder of your DNN instance.

The error message told me that anything is missed on the Manifest file, so you should check the Content of the Manifest file.

 Thank you again, Matthias. The modules in question were developed by a consultant and I have previously imported them OK (on different machines). They are not compiled. At this point I am stuck on this and have no idea how to move these modules to my new machine. The message doesn't given any clue about what exactly it wants that is not provided.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Import of custom module blockedImport of custom module blocked


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

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

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. 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.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out