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

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesOnly one module/extension per folder is stupidOnly one module/extension per folder is stupid
Previous
 
Next
New Post
3/14/2012 11:59 AM
 
I'm guessing this is something DNN does to make sure all modules have unique names based on module name and Path but if so, it doesn't seem like a really good solution. What we are trying to avoid is to have to place each module in a separate subfolder just to to please DNN, especielly since DNN only seem to be able to handle 2 levels when it comes to folders under DesktopModules. By disabling the indexs in the database we have worked around this and everything is working fine, but still, disabling functionality within Core isnt really all that fun...
 
New Post
3/14/2012 1:53 PM
 

Hello,

Again, this isn't a folders issue - it's a module names issue. You can't have two modules with the same name, and I would definitely not remove that index to get around that restriction. You CAN place two modules in the same folder.

The IX_Packages index, for example, makes sure you don't have two packages with identical names... This is logical, it would be like trying to install identical versions of Word on your computer twice or something.

Just name your modules different things and that will fix your problem. They can go in the same folder. For example, you could have a folder "DesktopModules/MyModules" and then install your "Store" module and your "Cart" module and place them in that folder. What you could not do is name your "Store" module and your "Cart" module both "MyStore." DNN would be unable to distinguish which is which... and I think that's what you're trying to do.

Mike

 
New Post
3/14/2012 2:20 PM
 
Not sure if you are trying to pull my leg here, of course you can't have to 2 files with the same name in the same folder, thats a file system restriction in every OS I've tried. Can't see how DNN could change that even if they wanted to.

Just try to place 2 files in the same directory and try to create 2 different extensions (module definitions) based on them and you will see that DNN (6.x) won't accept it. I'm quite certain that older version of DNN did though, but that was probably 4.0 and below.

What you can do is to have 2 different user controls in the same extension like ListProducts.ascx and EditProducts.ascx but of course that wouldn't be useful if the modules are not related to each other.


If you find a way to do it, please let me know because I would prefer to be wrong rather than having to modify the database :)
 
New Post
3/14/2012 2:22 PM
 

Patrik,

As Mike said, you can have multiple modules in a package and those modules can be under the same folder under DesktopModules. It really is just a matter of creating the .dnn manifest file correctly. take a look at the DNN blog module. ( DNN_BLOG.dnn file that shows multiple modules in one directory)

Hope this helps.

Good luck!

 


 
New Post
3/14/2012 2:25 PM
 

Hello,

No - sorry... just being dumb myself...

But yeah, again, I think you are mixing up the folder placement with the module name. The module name does not have to be the same as the folder. Consider the example below from a .dnn file. You can separately specify the folder and the module name. DNN is getting mad because you have the same module or package name - not because you are using the same folder. The IX_Packages index, for example, doesn't even include folders.

Mike

<package name="Example1" type="Module" version="00.00.03">
      <friendlyName>Example 1</friendlyName>
      <description>This is an example</description>
      <owner>
        <name></name>
        <organization></organization>
        <email></email>
      </owner>
      <components>
        <component type="Module" version="00.00.03">
          <desktopModule>
            <moduleName>MyExampleModule</moduleName>
            <foldername>MyModule</foldername>
            <moduleDefinitions>
              <moduleDefinition>
                <friendlyName>My Example Module</friendlyName>
                <moduleControls>
                  <moduleControl>
                    <controlSrc>DesktopModules/MyModule/ViewMyModule.ascx</controlSrc>
                    <controlTitle>My Module</controlTitle>
                    <controlKey></controlKey>
                    <controlType>View</controlType>
                  </moduleControl>
                  <moduleControl>
                    <controlSrc>DesktopModules/MyModule/EditMyModule.ascx</controlSrc>
                    <controlTitle>My Module Settings</controlTitle>
                    <controlKey>Settings</controlKey>
                    <controlType>Edit</controlType>
                  </moduleControl>
                </moduleControls>
              </moduleDefinition>
            </moduleDefinitions>
          </desktopModule>
        </component>
      </components>
    </package>

 

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesOnly one module/extension per folder is stupidOnly one module/extension per folder is stupid


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