Hi All,

Trying to find an answer to this question, can't find anything in the forum, closes I came was the feature request for for the module recycle bin.

I'm trying to remove some unused custom modules from my dev version of mojo (Just to tidy my dev folder up a bit) and I keep getting the following when I try to remove them in the admin tools.

This feature is being used in the content system. You must delete instances of this feature before you can delete the feature itself.

Iv'e removed all instances of the content from all pages that used it, and still when I click delete in the module admin panel I get the above message.  How do I remove old modules that I no longer need?

I know I can't just delete the files beacuse that will cause chaos.

Cheers

Shawty

Hi Joe,

Thanks for that.

I thought I was going insane, but now I see how the deletion system works, it makes a lot of sense.

Once again, thanks for a great CMS.

If your curious about my tweet I'll tell you what it was that won me out and made me choose mojo over Orchard.

Orchard can't do authenticated pages, that is I can't hide an entire menu option from a non-logged in user, only widgets in Layers and even then that can be by passed quite easily.

Cheers

Shawty

and a Fine job you've done.

I can also now reveal the main reason Iv'e been giving it so much attention.

I don't know if you are aware of "Lidnug" but to put it bluntly we are one of the Global .NET super groups for .NET developers, with (at last count) over 46,000 members world wide.

Our official home is on Linked-in ( http://www.linkedin.com/groups/LinkedNET-Users-Group-LIDNUG-43315 ) but we also have our unoffical home hosted by Orcsweb at http://lidnug.org/ 

Where currently running Sitefinity (Following a sponsorship from Telerik) but after having problems with version 4 we decided to find a new CMS.

As we have good contacts inside MS, and also know Bertrand-le-roy (the author of Orchard) we thought we'd give it a try, and it was great at first, until we started hitting snags.  Quite a few that where confirmed will be sometime before they'll be implemented and/or fixed.

As a result, I wen't hunting for something that would solve my issues in as quick and simple way as possible, and as a result we've chosen Mojo as our CMS.

The team that runs Lidnug are all experienced processional developers, but we run Lidnug in our spare time, and rarely have the time and resources to put masses of effort into keeping things running, esp since it's a non Profit making venture for the good of the community.

Iv'e also possibly persueded "david starr" of "scrum.org" fame to also use Mojo for there re-implementation after he asked my advice about CMS's a week or so ago.

I'm hoping to begin development sometime this week (Now I've more or less learned what I need to know) but it will be behind closed doors for a little while yet.

Once where up and running however, I'll happily fly the flag to show which CMS we are using, after all a good job, deserves some good come back.

Cheers

Shawty

I most certainly will do Joe.

Iv'e accepted your Linked-in request too.