Hi David,
That is interesting information you have uncovered. I initially thought I was looking for a piece of code causing the object reference error... it did not occur to me to check for the existence of all the SQL tables.
Too bad there isn't a simple import wizard of a database you can perform from the Web SQL admin tool. Probably by replicating a working local install and copying the SQL database as-is along with all the files, it would make installation much easier.
I agree, it appears GoDaddy is purposely not making this easy. What I'm wondering though is, what is the advantage for them to use the "automated install" approach of version 4.0.2? And also what I'm wondering is, if GoDaddy updates their DNN installation available (hopefully they would be putting 4.1 on the automated install package list soon), does it automatically update a version I've already installed with the older version... or would I be forever stuck using the version I have deployed?
With all these unknown questions in the air, it makes all the more sense to try and deploy a manual DNN installation for absolute full control.
I plan to make extensive use of DNN for my CMS solution both for myself and my customers, and I'd hate to be at the whim of whatever GoDaddy decides to do.
On the plus side though, I have been playing with the automated install solution of DNN, and it does work great... provided you access everything in your DNN solution through the DNN web interface.
I look forward to your next posting... as well as Michael's next post too for the latest manual install instructions.
- Andre