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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Short-term Job Offer : 4.0.2 Security Roles at SQL/Programmer LevelShort-term Job Offer : 4.0.2 Security Roles at SQL/Programmer Level
Previous
 
Next
New Post
3/20/2006 8:13 PM
 

Greetings to all of you Geniuses!

I've been using DNN 3x as part of my job for about a year. 
Recently, my boss demanded that we move everything to DNN 4.0.2 and so I did.
Unfortunately, I'm having trouble getting 4.0.2 to function like the 3x version which is currently in our production server.

Specifically, I'm having difficulty saving the edit rights checkbox values in module settings.  I check the ones I want, and click the Update link at the bottom of the settings page.  No error comes up but if I then go back into the module's setting screen, the edit rights checkboxes are all unchecked.

I'm considering two possible solutions. 

  1. If no one out there is experiencing this behavior, then there is something wrong with my environment.  In this case, I'm looking for someone who knows the DNN 4 enivornmental issues well enough to find the problem.
  2. If others have this issue, then it is an open item in DNN 4.0.2 (where do we report bugs to for DNN 4.0.2?)
    In the case of it being a bug, I need someone who understands 4.0.2 membership and security roles at the SQL level so that I can write an external program to edit my module security settings while I am waiting for the next DNN 4 release.

In either case, I need some help and my post about this issue over on the configure it forum hasn't gotten any replies.

To make things more intereting, my boss has gotten impatient and is now offering money to get this fixed.  He won't pay me anything extra, but if somebody can steer me towards a solution, that brilliant person will get paid.  I will also then make that person a paid-per-incident/hour consultant on or under the company books, so that I have someone to call when future issues come up.

I have the DNN set up on a server which is running RDP.  If anyone wants to log onto my server and share a session with me while talking on the phone (my boss will cover the long distance charges)

Please post back a reply with your name, applicable skills (can you handle option 1, 2 or both), your hourly/incident rate and whatever contact information you prefer.

Look forward to hearing from you.
Peace,

Colt

 
New Post
3/21/2006 1:03 PM
 

Sorry, I have to withdraw this job offer.  I figured it out and no longer need the assistance.

When I created my security role names, I wanted them to appear in a particular order, so I put a number and a colon before each name.  For example...

President
Secretary
Treasurer
Vice-President    (notice the wierd order when these values are alphabetized)

became...

01 : President
02 : Vice-President
03 : Secretary
04 : Treasurer      (which I thought looked a lot better)

unfortunately something about this (probably the colon) caused it not to save properly to the sql database.
Once I removed the numbers and colons, everything started working properly.

 

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Short-term Job Offer : 4.0.2 Security Roles at SQL/Programmer LevelShort-term Job Offer : 4.0.2 Security Roles at SQL/Programmer Level


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