Hi Crispy,
Thanks for the comments. I'm afraid it's not merely an opinion, but hard-won experience that makes me say it. The chap who started the thread above is obviously in the same boat that I and so many others have sailed in.
I've been over it many times and don't want to upset his thread here by going over it again in detail, but in my professional (and now also experienced) opinion, DNN will continue to fail a large number of people (who identify themselves as one of the intended audiences of the product) because it lacks an implemented communications strategy.
This thread here bascially results from that flaw, as do many of the others that I have read and assisted with over the past year and half that I've been inolved with DNN.
It's a cool product, but until someone in the core team finally sees the light, we will only have them telling new users that they must be inexperienced... it's called 'specialist arrogance' where I work.
In my view there is nothing in the DNN installation process that requires significant development expertise and could not be simply and logically documented and carried out by just about anyone with basic ftp and text editing experience. I had more than enough knowledge when I first started, yet the packaging, the documentation, the workflow logic, and the communications channels in and around the DNN community (not to mention some of the attitudes) all made the process very difficult and frustrating.
You'll know from previous chats that I'm a bit of a purist about these things. In communications I don't accept that there is such a thing as an inexperienced or un-knowing person... if they can't do something then they simply haven't been told correctly or clearly enough.
Anyhow.. hopefully someone will be able to sort out this chap's installation issue. I've gone for an obscure problem solution in my own efforts to assist because I'm pretty sure he isn't retarded.
Best regards,
Rob