I got the word this morning that I have to port all my websites to Joomla.  My hosting provider finally gave up on the lack of support offered for DNN, even though he had the paid version.  In my own experience, I have five unresolved issues, four of which never even rated a reply, and the one that did, led to a "do this", "it did that", "try this","I tried that","I give up".

I really liked DNN, but without any visible support, I recognize it's time to give up.

Hmm - honestly - sorry to hear you are leaving - but fwiw - there are MANY dnn hosting providers out there that KNOW how to support dnn.

DNN itself is a Community based product - and as such the support you see on these forums comes from volunteers and some very visible dnn team members like cathal and sebastian.

FIrstly, are your sites RUNNING - and able to be visited by people.

Seems to me if thats the case - then I would tell your hosting company - that you are happy with DNN and to NOT force you to move to joomla - because - i can give you any number of reason why you could become very unhappy with running on that platform.  A look thru the joomla forums - will see it full of many of the same questions you see on dnn forums.  With the same sorts of responses and feedback.

And, frankly, a host that cant make dnn working - should be looking more closely at themselves than blaming the product - take a look at powerdnn.com or dnn4less.com and maximumasp.com. these guys have tens of thosands of happy dnn sites running live and being accessed by millions of people every day.

Personally - I can usually get a dnn hosting up and fully installed with core access in around 10mins - with joomla make that about 35 mins to the same point.  

If you LIKE dnn - tell you host to get it sorted - its NOT acceptable for them to tell you what cms you should be using - OR move to a host that knows what they are doing - which would be my recommendation of the bat.

Westa

Sounds like a whole lot of complications that have more to do with the hosting company than the cms platform.

When you say you LOST your wiki or repository - that makes little or no sense - all the information is stored in a MS SQL database - unless someone at your host physically DELETED the data then its incredibly hard to understand how it could just be LOST.

I would be requesting a copy of the database/site BACKUP from the day BEFORE the wiki was LOST or the repository was LOST - because all that data will be there.

As for site logs - what do you mean you cant record site logs.  You can either use DNN's built in site logging tools - which just work out of the box - or the logging functions built into EVERY IIS web server that record every action into industry standard w3c compliant log file.

To be honest - sounds more and more like your hosting company is less than professional - or more probably an LINUX script kiddies house that needs its butt kicked for wasting your precious time and money.

Honestly - if it was me - I would have started legal action months ago to get your issues resolved.

As for owning a PAID VERSION of dnn - one would firstly have to ask WHY ???
And were they charging you for the privilege of using that PAID VERSION - the PAID version is licenced per domain pretty much - not something they can had out for free to end users ???

In the first instance - the logging question - NOT even sure how that relates to DNN - the web server usually handles LOGS not the CMS - although dnn can do internal logging as well - but most people who want log details tend to go straight to the IIS loging system,
Although - I would be worried - if they didn't know how to turn logging on inside DNN - its all of 2 mins work to activate.

Oh and if they DID request paid support - there should be a log of that request as well . . . and a request ticket.

With regard to LOST data - that strikes more of hosting company issues - or a simple failure to keep  backups that would resolve this sort of issues in seconds.

Westa