You know - as administrator or host - you will need to get used to seeing the *whole picture* when working when logged in. Sometimes this gives you the feeling that things aren't looking or working like they should.  There is no reason to *remove* these features, but you can hide them.  So it means that your users and website visitors don't see them, but when logged in they are visible.  Sometimes when I am testing a site I create a testing person and log in as them, to see what the public sees.

So, how did you remove them? Through the ascx file?  That would surely cause you some headaches and that's not also how you add properties either.

Although this is the wrong forum post this in, you might like to start a post in the Lets chat about it Forum or the Configure it Forum and specify exactly what you want to achieve, and we can answer the questions there.   And, also people doing that sort of thinking aren't always visiting the skinning forums.

Nina Meiers

Thanks nina, so basically you say that i should work on top of the current properties, without deleting them. It's frustrating since i have a couple of sites waiting in stand by for a masive deployment to dotnetnuke, but since everytime i try to modify this properties the whole site gone numb...i actually have to reinstall DDN...cant go thru that with a site of 2000 users.

Anyways, it seems like no body else is fighting this issue...so ill work as stated. Kinda makes no sense to use an app like DDN that features users properties but you really cant play with it. Its like a new car with power windows but dont use them cause the battery will go out. ja.

If anyone figures this out please let me know....hoping i dont have to move to mambo... :(