OK, this was it =)...I placed the Login Snippet in the login page as follows
[[!Login? &loginResourceId=`3`]]
and now it’s working as expected! Thanks for that...to conclude, this means a backend login doesn’t equal a frontend login...should maybe placed somewhere in the docs, or did I just overread that?
thanks for your help!
Another thing I would be interested in is if I couldn’t show the 403 or the login page (which could be the same...) instead of the 404 page. I believe to have read something from you like a "...in a following tutorial", is there already something online about this topic?
EDIT: The info in your tutorial was enough =)...just granted the (anonymous) User Group "Load Only" Access in both the Context Access and Resource Group Access (are they both necessary?)
EDIT2:
Another problem... I don’t know where the error page btw. its content comes from...I specified the error_page context setting for the "admin" context, its pointing to the login resource and the system error_page setting points to resource 1 which has other content than the shown "Unauthorized - You are not authorized to view the requested content."...where does this come from and how can I customize it?
...solved: I needed another context setting called "unauthorized_page" for the context "admin" which points to the login resource...don’t know why the public page with resourceid 1 (standard) doesn’t work here...because I can access this page without problems when not logged in...