changes to how "unauthorized_page" works in revo?

under "system"->"system settings"->"site" i have "unauthorized_page" set to "3", which is a page that exists, and is published, but whenever i try to access a page (front end) that is protected, i am instead redirected to the "error_page" value, which is set to "2".

i’ve attached a screen shot. for example "resume (4)" has an access permission set, but when you try and access the page (front end) you’re redirected to "404 (2)". am i missing another setting somewhere? always had this working in evo by changing that one value.

the 404 page i created is working fine, and comes up when expected.

See Unauthorized VS Error Page here: http://bobsguides.com/revolution-permissions.html

bob,
thanks for that - it helped. here’s what i did in case anyone else is having the same issue:

1) go to "Security"->"Access Controls"->"User Groups"
2) right-click on "(anonymous)", choose "Update User Group"
3) go to "Resource Group Access", and "Add Resource Group"
4) set "Resource Group" to the group in question (in my example "professionalPages")
5) set "Minimum Role" to "Member - 9999"
6) set "Access Policy" to "Load Only" (which should have been created on install)
7) set "Context" to "web"
8) "Save"
9)"Security"->"Flush All Sessions"

reload page on front end. seemed to work for me, domain.com/professional/resume now redirects me to my login page thanks bob!

Glad you got it working. Thanks for reporting back.


I’m sure the steps will help people.

your guide helped a lot, though i’m thinking you may have written it during an "rc", because my "pl" version of modx revo came with a "load only" access policy already created. your tutorial just had more steps than were actually necessary.

thanks for your help. i’m really loving revolution so far, but after having used evo for so long, the differences take a little getting used to, especially with the vastly superior (and more complex) acl system.