Removing "Public Access" doesn't work on fully secured site
I'm using Umb v3.0.5. Assume the following (desired) content tree.
Content - Home (restricted to only group members) + Intro (restricted to only group members) + Steps (restricted to only group members) + Help (restricted to only group members) + Tools (public) -- Login -- Register Now -- Forgot Password
As you can see, I am building a secured site with just a few public pieces to allow people to get started. To implement this, I have used advanced "public access" and secured every from the home page level on down to group "members". The problem my Tools area. I need that to be publically available so people can register or retrieve a forgotten password.
When I right-click, "public access" on Tools I click the "Remove Protection" button. It returns and says "Removed Protection from Tools". Alas, it did not. Register now is still protected and simply forces the login page first.
What am I doing wrong? Tell me he is not assuming everyone underneath is protected.
Thanks in advance, Jim
P.S. I am techie enough so if this is bug, please explain how to backdoor this through the database or access.xml if that is necessary. I'm unclear on the role of access.xml since I deleted it and it does not get recreated even when I publish all, repub entire site or set "public access" on a node.
I am afraid that public access _is_ inherited as far as I know. I haven't used it that much, but this might be a usable workaround:
Content - Landing (Public, but redirects to "Home") + Home (restricted to only group members) + Intro (restricted to only group members) + Steps (restricted to only group members) + Help (restricted to only group members) + Tools (public) -- Login -- Register Now -- Forgot Password
Could that work for you?
Anyways, I think it might be a good point that you should be able to override protection on a subpage, so you could add that as a request on Codeplex.
Removing "Public Access" doesn't work on fully secured site
I'm using Umb v3.0.5. Assume the following (desired) content tree.
Content
- Home (restricted to only group members)
+ Intro (restricted to only group members)
+ Steps (restricted to only group members)
+ Help (restricted to only group members)
+ Tools (public)
-- Login
-- Register Now
-- Forgot Password
As you can see, I am building a secured site with just a few public pieces to allow people to get started. To implement this, I have used advanced "public access" and secured every from the home page level on down to group "members". The problem my Tools area. I need that to be publically available so people can register or retrieve a forgotten password.
When I right-click, "public access" on Tools I click the "Remove Protection" button. It returns and says "Removed Protection from Tools". Alas, it did not. Register now is still protected and simply forces the login page first.
What am I doing wrong? Tell me he is not assuming everyone underneath is protected.
Thanks in advance,
Jim
P.S. I am techie enough so if this is bug, please explain how to backdoor this through the database or access.xml if that is necessary. I'm unclear on the role of access.xml since I deleted it and it does not get recreated even when I publish all, repub entire site or set "public access" on a node.
I am afraid that public access _is_ inherited as far as I know. I haven't used it that much, but this might be a usable workaround:
Content
- Landing (Public, but redirects to "Home")
+ Home (restricted to only group members)
+ Intro (restricted to only group members)
+ Steps (restricted to only group members)
+ Help (restricted to only group members)
+ Tools (public)
-- Login
-- Register Now
-- Forgot Password
Could that work for you?
Anyways, I think it might be a good point that you should be able to override protection on a subpage, so you could add that as a request on Codeplex.
Thanks tons! I just ran through this. Your solution worked like a champ. Life is good again.
Thanks,
Jim
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.