Robb
|
How do you get rid of the login in the menu? I *do* need login and registration capabilities, but I don't want it in the menu.
|
| |
Jonatan Rullman
|
Hi!
I actually had a support request answered yesterday about this. There are a few posts in the forum that details it but they aren't very specific and even as an advanced user i couldn't figure it out.
It's really pretty simple. First of all, add a login module like you would any other module. I've experienced that it does behave a little different but that might be just a glitch in my config.
Second, export your skin with Artisteer, open the Zip file and extract skins.zip. Then open skins.zip and extract the page.ascx file.
Open it with notepad and find the line that starts with "<dnn:ARTMENU"
In it you will find "ShowLoginTab="True"" and "ShowUserTab="True""
Since i havn't had the time to try it myself i don't know if you have to change them both to FALSE or if login sufficies but im guessing that will be easy enough to find out on your own.
Finally, save the file and insert it into skins.zip which you then insert into your exported zip file, saving both of them of course, and then you should be done. Just uoload in like normal.
What i really would like to know if why the other three values in the <dnn:ARTMENU are configurable through the interface and not these two or why, at least, you can't change them during export.
Cheers
|
| |
Jonatan Rullman
|
Hi!
Sorry, i just relized my instructions were for dnn 4.
Dnn 5 follows pretty much the same guidelines, only there aren't a skins.zip in the main zip file so skip that step and go straight to page.ascx.
Cheers
|
| |
robb
|
got it... thanks... I shoulda known that.
|
| |
Craig
|
HI,
My problem in 2.3 is that login and register appearing twice on the menu when I add the DNN modules. Doing as you suggested, I set the tabs to false, which removed the duplicates but also the logout button on the menu. Resetting the logintab to true restores the logout button, but login still appears twice.
Any ideas?
Thanks.
|
| |
BrianM
|
I hate cluttered interfaces, so in designs where I don't want the design/space overhead, I embedded the log-in/llog-out (can also be applied to Search) specific structures in an ID'd div element and set that element's position to absolute (removing it from the normal page flow objects) and set the css id selector's property to display:none; .
Then it is a simple matter of in-page Javascript to enable whatever "triggering" mechanism (word, image, etc.) that the design calls for by attaching the hide/show function to the objects onclick event. use the title attribute to provide for user feedback via a tooltip.
This is a simple approach and can be implemented fairly straight-forwardly. A more robust method would be to open the pageit in Visual Studio and creating the proper behaviors etc. that you desire with some object code-behind.
|
| |
willard31
|
BrianM,
That is a very interesting approach which I think I would like. Could you provide a link to a site where you have done the login this way?
thanks
|
| |
tim
|
i dont understand creating the login like any other module? There is no login module?
|
| |
Roger Sramkoski
|
Tim,
He means the Account Login module.
Jonatan Rullman,
Setting ShowLoginTab to False removes the login/logout tab as I'm sure you guessed. Setting the ShowUserTab to False removes the register/'user profile' tab, which isn't quite as clear or obvious. The User tab will take on the user's account name when the are logged in, allowing them to modify profile settings.
I also like to keep my menu bar clean and one thing I have done in the past is add the Login/Logout link and Register/'Username' link to the left of the breadcrumb trail separated by | characters. What you end up with is a row that looks like this:
Login | Register | You are here > Home
To do this you have to add this line near the top of the skin's page.ascx file with the other Register lines:
<%@ Register TagPrefix="dnn" TagName="USER" Src="~admin/Skins/User.ascx" %>
Then scroll down in your page.ascx file until you find the line that has:
<dnn:TEXT runat="server" id="dnnTEXT" Text="You are here >" ResourceKey="Breadcrumb" /> <dnn:BREADCRUMB ID="dnnBREADCRUMB" RootLevel="0" Separator=" > " runat="server" />
Add this line of code in front of that on the same line (my tests of cleaning the code by putting it on separate lines led to bad things, so keep it on the same line) and note there is a space after the | character:
<dnn:LOGIN runat="server" ID="dnnLOGIN" /> | <dnn:USER runat="server" ID="dnnUSER" /> |
|
| |
tim
|
Sorry to coniually post, but where is the account login module? in DNN.
|
| |
Roger Sramkoski
|
Tim,
Are you familiar with how to edit pages and add any modules? If not, you may need to take a step back and learn that first. If you do know how to add modules to pages then you should find the Account Login module in the same drop down list as all the other modules when editing a page.
- Roger
|
| |
Gabby
|
FYI - In page.ascx, you can place the login whereever you like. The code that references the login/logout is:
<dnn:LOGIN runat="server" ID="dnnLOGIN" />
For instance, I placed mine in my footer next to "Terms of Use" and "Privacy Statement". The following will display "Terms of Use | Privacy Statement | Login".
<div class="art-Footer-text">
<p><dnn:TERMS runat="server" ID="dnnTerms" />
| <dnn:PRIVACY ID="dnnPrivacy" runat="server" />
| <dnn:LOGIN runat="server" ID="dnnLOGIN" /></p>
</div>
-Gabby
|
| |
Gabby
|
I should have also added that if you use the method I described above, you won't need to add the Account Login module. It automatically uses it when you click "Login".
-Gabby
|
| |