Sure, but what if you wanted to have a folder called "Modules" and then put in a few other user controls in there that had nothing to do with the blog-module at all, like say a Twitter module. Natrually you wouldn't want them to be the same extension in DNN and then the problems starts. At least I know of no way to do it, but that doesnt mean there is not such solution _)

 The problem is that DNN never asks me for Package names when I choose "Create new module" under Extensions. I haven't check this but I assume it takes the foldername which creates a problem the next time I try to create a module from the same folder. You can of course change this in the database afterwards, and that is perhaps better than disabling indexes, but it still feels like a stupid limitation

Patrik (and any other future user who finds this),

Again, under absolutely no circumstances ever... ever... should you remove those indexes to "fix" this problem. It is definitely not a "fix" and you will regret it... That fix is far stupider than the problem you are claiming exists.

The web interface's "create extension" process is very simple and not really meant for anything very fancy. You simply need to do a little work to the output from that wizard, or learn how to write your own manifest file from the documentation. You just seem to be entirely uninterested in actually learning how to fix this issue. A number of us here have provided you with the correct answer. The worst thing you can do here is to keep suggesting that removing that index is a useful fix. It will cause you to face problems later and it would cause other unfortunate users to face problems later.

In short - please don't remove that index...