Quote from: BobRay at May 18, 2016, 11:11 PM
@SyberKnight -- both of those properties take a Resource ID for their arguments.
Also, &redirectToOnFailedAuth can't be used to redirect to the current page.
The page you redirect to needs to be published and accessible by anonymous users. It probably also needs to be in the main front-end context ('web').
thanks for piping in, but these are things i actually DO know (LOL - as opposed to the many many i don't).
i only wrote the above with pound/hash/number symbol instead of the numbers i use because everyone has different numbers. i do have the proper numbers in there for my resource id's.
also note, i'm not trying to redirect to the current page. i have separate "error" pages setup with (hopefully) helpful tips on why the user may have gotten there & how to remedy the issue. and they are published & accessible & front-end'ed.
even still, when i test for the errors, the 404 page always overrides the redirectToOnFailedAuth page.
and as far as the redirectToPrior goes, it just never worked. after login, it would just redirect to the homepage. so i'm using the loginResourceId to make it redirect to the page of my choosing instead.