FrontEnd Users (Members) --- Access denied message

[doctor]

Hi, I ran into this annoying problem, when

- I created a member and a group he would belong
- then protected a page (published) in the Site Structure by assigning it to this group
- with all this done, I checked if said page would appear in the menu (did not, which is expected)
- the this new member logged in
- the menu item associated with this page appeared( expected)
- PROBLEM: upon the member got logged in the following message appears in the main content window (not expected):

Access denied!
You are not allowed to access the requested page!

Maybe you are not logged in correctly?

If a user tries to access a protected page without permission, a special error_403 page will be called. In this case you can either display an error message (like we are doing now) by simply creating an article on this page, or you can redirect the user to another page (e.g. the welcome page).

Accordingly, if a user tries to access a page that does not exist, a special error_404 page will be called. Again, you can either display an error message or redirect the user to another page.

- otherwise everything seem working all right.

Thanks for your help in advance!

[mechaflash]

-You created a member (member1) and created a group (group1)
-You assigned member1 to group1
-You protected the page and assigned group1 to only view it.
(and to clear up confusion...)
When logging in with member1, you see the error message?
OR
When navigating to the protected page while logged in with member1 you see the error message?
OR
When on protected page while logged in with member1, the "MAIN" column shows the error message?

By your post it sounds like the 3rd choice, and if so...
1) Make sure you did not set protection for the articles/elements on the page (only need it for the page itself)
2) Ensure you have not created an article in the main column of that page stating: "Access denied! You are not allowed to access the requested page! Maybe you are not logged in correctly?" XD

Try un-protecting the page and then navigating to it and see what happens.

[doctor]

Thanks for your feeedback. The error message appears once member1 logs in irrespective where he is before his logging in. On cannot be on the protected page before member1 logs in because that page will not show.

-You created a member (member1) and created a group (group1)
-You assigned member1 to group1
-You protected the page and assigned group1 to only view it.
(and to clear up confusion...)
When logging in with member1, you see the error message?
OR
When navigating to the protected page while logged in with member1 you see the error message?
OR
When on protected page while logged in with member1, the "MAIN" column shows the error message?

By your post it sounds like the 3rd choice, and if so...
1) Make sure you did not set protection for the articles/elements on the page (only need it for the page itself)
2) Ensure you have not created an article in the main column of that page stating: "Access denied! You are not allowed to access the requested page! Maybe you are not logged in correctly?" XD

Try un-protecting the page and then navigating to it and see what happens.

[mechaflash]

A few things comes to mind...

Check your Member Group policies and see if you specified a "Redirect to page..." for that group. If you want the member to be on the same page they logged in on, turn off the Redirect option. Else, choose a page that is live for them to redirect to.

Another one is to check each page in your Site Structure and make sure that you don't have them set to "Show to Guests Only". This may also cause the error.

While you're in your Site Structure, check the pages at the Access Protection -> Allowed Member Groups and make sure you have your 'Group1' selected.

Then go to your Members and make sure that Member1 is in Group1.

This error usually pertains to not have sufficient rights to access the page. To my knowledge, these are the things that would effect that.

[doctor]

Thanks for your suggestions.

In fact that I found out as a solution was that the member MUST BE redirected to an existing page upon loggin in. Otherwise the engine disregards the member's login status and regards the first attempt of loading the actual page as unauthorized.