leupold wrote
what a rubbish. set the registration mode to none to remove the "register" link. Afterwards you can place the login link whereever you want - it will be useless for any visitors. Adding a logout link to the admin menu will provide this option only to members of the Administrators role - and when using DNN as CMS, it is not recommended to grant all users involved in the workflow admin permissions.
Rubbish? Is that a way to treat someone who is trying to share? Maybe it was just the wrong english word, but I have a feeling it would be even more harsh in german.
It's not rubbish, it is a community member sharing the way they have solved a particular problem. And taken the time to explain in detail how they went about it.
I like these kinds of posts, because they can lead to lots of other ideas, or things we have never thought about.
There are usually many ways to solve a particular problem, and one way is usually not more right than others.
I actually approached this a little differently, mainly because the customer asked for it this way. I made the login link the same color as the background and then absolutely positioned it to an easy to find place (for them) beside their logo. Now they know where to click to login, and the same place is used to logout (if they decide to logout instead of just closing the browser).
Now, for a question on your solution Sebastian.
Why would you remove registration and still keep the login link visible?
Are you wanting to frustrate the end user, making them think, hey there is a place to login, but where is the registration, it must be here somewhere?
What if I still want to allow registration for selected people, but not for the general public?
The other idea about doing it on a different hostname was good too.
Don't let Sebastian keep you from posting your ideas everyone, his is only one opinion.