Hi,

you can solve it by redirecting the  logged in user to the  "header + content + footer" page. So you should have two pages, one(with content) for logged in user and other(login module) for the visitor.

Regards.

However if you do that and the logged in user types the url to home again he will land on the default page which is the one with the login form. Or is there a possibiliity to change an item in the menu based on login status?


---EDIT
Would it be viable to go into the code of the login form and get an if else statement in there that checks the current user(if there is no current user that means he is not logged in ) or would that not be adviseable

Hi,

login page should have redirect logic. And even if the logged in user types "login page" url he will be redirected to other page..

Yes, you can set the visibility of the MonoX menu item in the administration. Take a look at the attached screenshot. The idea is that each logged/registered user is set to the appropriate role. Therefore you can use that role to filter users which can see the menu item.

Regards.

{1}

##LOC[OK]##

{1}

##LOC[OK]## ##LOC[Cancel]##

{1}

##LOC[OK]## ##LOC[Cancel]##

Attached files

I understand that the login page has redirect logic but im not using the login page, i have added a login field module to the landing page and using that. with " the logged in user types the url to home again" i ment that the user goes to the base url www.mysite.foo. by doing so he lands on the landing page wich has the login field module. even if he is still logged in in the current session.

The screenshot did help with editing the menu thanks for that.

Also im seeing Codebehind="LoginModule.ascx.cs"  in every module but then visual studio says this file cannot be found. i imagine these to be the actual controller behind the view page. are these only accessable if you have the source version?

Hi,

if you do not want to have separate login page and handle redirects(you want login module on home page which is visible depending on the current user) you should register login module control in your page markup and handle the visibility logic in the  code behind(.cs file).

If you are using existing MonoX page you should add the code behind file(that means extend the existing page/control) and handle visibility logic there. An example "OnPreRender" page event.

Source code edition allows you to take advantage of the .cs files. Free version does not contain .cs files, but you can still extend the existing functionality. Click here for an example on how to do it.

Regards.