Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Help urgentHelp urgent
Previous
 
Next
New Post
10/24/2007 11:13 AM
 

Someone could have told us that DNN doesnt use the signin.ascx anymore and automatically refers to the elogin instead!

Just had to remove the reference to the signin.ascx at the top of each skin file

 

Thanks


Class Campers -The Home of the Volkswagen camper & Bus Enthusiast
Worlds Cheapest Homes - Need a Cheap Property, cant afford a home
Beeb iPlayer - Need help with the BBC's new iPlayer software
Internet Insurance Quotes - For the the information you will ever require about Insurance
 
New Post
12/26/2007 5:20 PM
 

I am getting this error too and I went from v4.05.03 to 4.06.02.  Now I cannot build and get this error... Among many others.  I would rather know how to upgrade this portal, rather than install it, as I need to upgrade a production version of it based on my experiences with the non-production copies.


Will Strohl

Upendo Ventures Upendo Ventures
DNN experts since 2003
Official provider of the Hotcakes Commerce Cloud and SLA support
 
New Post
12/28/2007 4:15 AM
 

If you use the install package you just have to edit the new web.config with the settings from you old web.config:
Before you start make sure you have an offline copy of the existing web.config as well as a backup of both the dotnetnuke-dir and the database.

copy the contents from existing web.config to new web.config for the flw.

1 . <connectionstring>
2.<appsettings>
3.<machinekey>

ftp all the files from the install-package + the new web.config to your server.

And your portal is upgraded and working.

 
New Post
12/28/2007 10:56 AM
 

Will Strohl

Upendo Ventures Upendo Ventures
DNN experts since 2003
Official provider of the Hotcakes Commerce Cloud and SLA support
 
New Post
1/21/2008 5:16 PM
 

I had this going from 4.6 or 4.7 to 4.8. I had copied my settings from the old web.config to the new release.config & named it back to web.config, used the "Upgrade" package and got that dread:

My solution, as presented above, was also to remove the following line from to top of my skin's .ascx file (under /Portals/_default/Skins/mySkinName/mySkinType.ascx):

<%@ Register TagPrefix="dnn" TagName="SIGNIN" Src="~/Admin/Security/Signin.ascx" %>

I did not have to remove those other files. Thanks for the help!

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Help urgentHelp urgent


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out