We are excited to announce that the ASP.NET Forums are moving to the new Microsoft Q&A experience. Learn more >
dnn 3.0.13 installed, but acting strangely
2 replies
Last post May 10, 2005 11:39 AM by uniquehandle
Last post May 10, 2005 11:39 AM by uniquehandle
None
0 Points
8 Posts
dnn 3.0.13 installed, but acting strangely
May 08, 2005 07:48 PM|uniquehandle|LINK
I wanted to edit the text in the content pane, as you know it installs with some dnn boilerplate about changing the admin pswd and so forth. Oddly, the edit page I reached after clicking on the "edit text" link was blank...ie, none of the boilerplate dnn content was there. Also I found I couldn't type anything into the "Edit Text/HTM" form that appeared. I canceled this form and the orig content pane text was retained. I tried to "edit text" again, but this time hit update to see if it would kill the dnn boilerplate. Sure enough it's all gone. Still can't edit.
What is the "secret" that allows this most basic funtionality to work?
A pretty wierd start.
Browser is IE 6.
Thanks
None
0 Points
415 Posts
Re: dnn 3.0.13 installed, but acting strangely
May 09, 2005 12:44 PM|phr0ze|LINK
Free DotNetNuke News, Tips, Strategies and more.
www.dotnetnukesites.com
None
0 Points
8 Posts
Re: dnn 3.0.13 installed, but acting strangely
May 10, 2005 11:39 AM|uniquehandle|LINK
First time I set up dnn, edits to the portal elements are a combo of disabled and destructive, as previously noted.
Second time I set up dnn, all of the images are lacking from the main portal; came out much worse than the first time.
Help for setting up. Well, for the last three days or so, the first link in the getting started section on the dnn site has been dead via IE or some strange error about cookies, redirection etc. The rest of the faqs listed seem very skimpy, and have lead me to the current impasse. Most of the resources that look more complete are for sale.
Posted here and got one response, to reinstall, and while I appreciate that, it's a little underwhelming.
I'll figure it out eventually but these sorts of out of the gate failures are not what I expected from what is supposed to be the premier open .net effort.