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 ...Source Upgrade 4.8.2 to 4.9.0, All Administrator role users no longer have administrator privilegesSource Upgrade 4.8.2 to 4.9.0, All Administrator role users no longer have administrator privileges
Previous
 
Next
New Post
12/9/2008 2:37 PM
 

I need to use this issue in Gemini as a reference as the issue has been wontfix'ed by the DNN team.

http://support.dotnetnuke.com/Default.aspx?p=2&i=8430

The current situation we have is that we just did a source-based upgrade from 4.8.2 to 4.9.0 and all users that had Administrator role lost all Administrator privileges (even the built-in admin user), which basically means that if you now log in with any of the existing admin users (haven't tried creating a new one), they do not get the Admin menu, nor the ability to edit module settings, pages, etc.  The DNN team is saying that is is somehow a data corruption, but that would mean the data would be corrupt in all of our installs (that were created separately) including local development machines.  I say that it is data corruption caused by the upgrade and that it should be treated as a defect.  Regardless, this is a complete show-stopper for us, but not considered a defect to be listed in Gemini.  So, I come here to plead for help as we cannot figure out what the problem is.

We use a version control system to deal with the fact that we are building DNN from source.  This allows us to make sure that we know exactly what has changed in the new copy of the source compared to the one we are building from.  We have been doing this for more than a year now since 4.6.0, I believe, and have had very few problems.  However, this latest upgrade effectively destroyed the Administrator role and we are not sure how it even happened.  From what we can tell, everything seems in tact (database, DLLs, etc).

Any ideas?

 
New Post
12/9/2008 5:00 PM
 

If this is a case where it's for Portal 0, this was a fairly easy fix for me.  Check the thread that I originally attached to the issue.  As I recall, I had to get into the database and change just a few fields to get in.  Then I could use the DotNetNuke Host configuration to fix it.




Joe Craig
Patapsco Research Group, Ellicott City, MD
DotNetNuke Development and Services (http://patapscorg.com)
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Source Upgrade 4.8.2 to 4.9.0, All Administrator role users no longer have administrator privilegesSource Upgrade 4.8.2 to 4.9.0, All Administrator role users no longer have administrator privileges


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