February 09, 2010

DNN 5.2.x Changes to Module Create Process

In a few of the most recent versions of DotNetNuke, major changes have been completed in the way that a user manually imports a module definition to test a manifest file.  This is specifically the process that is mentioned in my book to test a module while developing, before it has been packaged for installation on another portal.  From what I gather, the behavior might change back a bit, but for now the process is slightly different that indicated in my book.  In this blog posting I'll document the changes, and a workaround solution.

The Old Way

In the book, the documented process for importing a manifest was to go to "Host" -> "Module Definitions" then select "Import Manifest".  This option to import the manifest has been removed, therefore the instructions in the book will NOT work.

The New Way

The modifications that were included in the 5.2.x versions of DotNetNuke have made this process more complicated to complete and moved it to a new location.  I believe this is part of future plans to help improve the process.  Sadly, I didn't notice this change until individuals started writing in with complaints.  Below is a list of steps now necessary to import a module definition using the new process.

  1. Navigate to Host => Module Definitions
  2. From dropdown menu select, 'Create New Module'
  3. Select Create Module From: Manifest
  4. Owner Folder: <Not Specified>
  5. Module Folder: (Put your folder here...)
  6. Resource: (Put your dnn file here...)
  7. Leave Add Test Page unchecked.
  8. CLICK Create Module

Following these steps you will import the module definition, in the end completing the same process as what was done before with the "Import Module Definition" option.

I hope this helps anyone that is following along with the book!

tags: DNN, DNN Development
comments powered by Disqus

Content provided in this blog is provided "AS-IS" and the information should be used at your own discretion.  The thoughts and opinions expressed are the personal thoughts of Mitchel Sellers and do not reflect the opinions of his employer.

Content Copyright

Content in this blog is copyright protected.  Re-publishing on other websites is allowed as long as proper credit and backlink to the article is provided.  Any other re-publishing or distribution of this content is prohibited without written permission from Mitchel Sellers.