Code Comments
Programming Forum and web based access to our favorite programming groups.
Navigation tree problemsHi Is it possible to display different navigation trees for different users. Actually I have separate branches created for each group of users. My requirement is that for each user the navigation tree should show the documents of the branch to which that particular user has access to and should not show any documents he is not allowed access to. -- Thanks & Regards Manoj My Corporation
Post Follow-up to this message
RE: Navigation tree problemsWhat didn't work about setting that through the ACL, Manoj? Zack Mentz Technical Document Analyst Liquent Thomson Scientific zachary.mentz-L+G57L1VLRZBDgjK7y7TUQ@public.gmane.org <mailto:zachary.mentz- L+G57L1VLRZBDgjK7y7TUQ@public.gmane.org> www.liquent.com <http://www.liquent.com/> http://scientific.thomson.com <http://scientific.thomson.com/> ________________________________ From: daisy-bounces-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org [mailto:daisy-bounces-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org] On Behalf Of Manoj Yadav Sent: Tuesday, June 10, 2008 11:00 AM To: daisy-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org Subject: [daisy] Navigation tree problems Hi Is it possible to display different navigation trees for different users. Actually I have separate branches created for each group of users. My requirement is that for each user the navigation tree should show the documents of the branch to which that particular user has access to and should not show any documents he is not allowed access to. -- Thanks & Regards Manoj My Corporation
Post Follow-up to this message Re: Navigation tree problemsManoj Yadav wrote: > Hi > > Is it possible to display different navigation trees for different > users. Actually I have separate branches created for each group of users. > My requirement is that for each user the navigation tree should show the > documents of the branch to which that particular user has access to and > should not show any documents he is not allowed access to. Take a look here: http://cocoondev.org/daisydocs-2_2/373-cd/19-cd.html ________________________________________ _______ daisy community mailing list Professional Daisy support: http://outerthought.org/en/services...rt.html mail to: daisy-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org list information: http://lists.cocoondev.org/mailman/listinfo/daisy
Post Follow-up to this message Re: Navigation tree problemsHi The problem I am facing is that I have configured say 5 branches. Now I am creating an administrator for each of these branches. In the navigation tree I have links to 5 documents that query daisy for that particular branch on display the results on a page. Now my requirement is that each administrator should not be able to see the links of the other 4 documents in the navigation tree and should only see the link of the document that displays the contents of this branch. Now using ACL I configured a role cosite_admin and for this role I revoked all the permissions including the read permission for all the doucments. Then I created another rule saying that if a user admin1 belonging to role cosite_admin role is there then I granted him complete access to his branch for e.g. branch1 The problem is since I revoked all the rights on all the pages except his branch , after logging in using the admin1 id I get the message No sites are available to you . In other words the sites welcome page is no longer accessible for this user. So nothing comes up in the navigation tree as well so the navigation tree is not accessible either . On Tue, Jun 10, 2008 at 8:42 PM, <zachary.mentz-qs4m+OjfQoH+fug3k4jHmNBPR1lH 4CV8@public.gmane.org> wrote: > What didn't work about setting that through the ACL, Manoj? > > > > *Zack Mentz* > Technical Document Analyst > Liquent > > *Thomson Scientific* > > > zachary.mentz-L+G57L1VLRZBDgjK7y7TUQ@public.gmane.org > www.liquent.com > http://scientific.thomson.com > ------------------------------ > > *From:* daisy-bounces-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org [m ailto: > daisy-bounces-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org] *On Behal f Of *Manoj Yadav > *Sent:* Tuesday, June 10, 2008 11:00 AM > *To:* daisy-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org > *Subject:* [daisy] Navigation tree problems > > > > Hi > > Is it possible to display different navigation trees for different users. > Actually I have separate branches created for each group of users. > My requirement is that for each user the navigation tree should show the > documents of the branch to which that particular user has access to and > should not show any documents he is not allowed access to. > > > -- > Thanks & Regards > > Manoj > > My Corporation > > ________________________________________ _______ > daisy community mailing list > Professional Daisy support: > http://outerthought.org/en/services/daisy/support.html > mail to: daisy-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > > -- Thanks & Regards Manoj My Corporation
Post Follow-up to this message RE: Navigation tree problemsI think I understand. This is an ACL issue. ACL is evaluated from top down. If there's conflicting statements, whichever one is on bottom will win. Also, any statements that restrict the role of "administrator" aren't going to work since administrators always have full rights. You said you're using a different role, cosite_admin, so I think you're fine there, but just to be clear. I've done something similar with our own instance of Daisy, but instead of restricting based on branch, I restricted by collection. My first statement looks like this: If true then everyone Read Live(X) Read(X) Write(X) Delete(X) Publish(X). This shuts off all sites to all viewers except admins. My next line opens up one site to one role, it looks like this: If collections = 2 then Role: product_management Read Live(check) Read(check) Write(check) Delete(check) Publish(check) So now anyone in the product_management role should be able to log in and see only the site that is part of collection 2. And just repeating statements like this downward with different collections and roles gives me something similar to what I think you're looking for. I think you might find it easier (if you're not doing so already) to break those things up into different sites and collections instead of querying on branches. That'll give you freedom to add one document to several collections if you ever decide you want to share certain documents between roles (and you wouldn't have to edit the ACL). Just a thought. Zack Mentz Technical Document Analyst Liquent Thomson Scientific zachary.mentz-L+G57L1VLRZBDgjK7y7TUQ@public.gmane.org <mailto:zachary.mentz- L+G57L1VLRZBDgjK7y7TUQ@public.gmane.org> www.liquent.com <http://www.liquent.com/> http://scientific.thomson.com <http://scientific.thomson.com/> ________________________________ From: daisy-bounces-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org [mailto:daisy-bounces-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org] On Behalf Of Manoj Yadav Sent: Tuesday, June 10, 2008 12:10 PM To: Daisy: open source CMS - general mailinglist Subject: Re: [daisy] Navigation tree problems Hi The problem I am facing is that I have configured say 5 branches. Now I am creating an administrator for each of these branches. In the navigation tree I have links to 5 documents that query daisy for that particular branch on display the results on a page. Now my requirement is that each administrator should not be able to see the links of the other 4 documents in the navigation tree and should only see the link of the document that displays the contents of this branch. Now using ACL I configured a role cosite_admin and for this role I revoked all the permissions including the read permission for all the doucments. Then I created another rule saying that if a user admin1 belonging to role cosite_admin role is there then I granted him complete access to his branch for e.g. branch1 The problem is since I revoked all the rights on all the pages except his branch , after logging in using the admin1 id I get the message No sites are available to you . In other words the sites welcome page is no longer accessible for this user. So nothing comes up in the navigation tree as well so the navigation tree is not accessible either . On Tue, Jun 10, 2008 at 8:42 PM, <zachary.mentz-qs4m+OjfQoH+fug3k4jHmNBPR1lH 4CV8@public.gmane.org> wrote: What didn't work about setting that through the ACL, Manoj? Zack Mentz Technical Document Analyst Liquent Thomson Scientific zachary.mentz-L+G57L1VLRZBDgjK7y7TUQ@public.gmane.org <mailto:zachary.mentz- L+G57L1VLRZBDgjK7y7TUQ@public.gmane.org> www.liquent.com <http://www.liquent.com/> http://scientific.thomson.com <http://scientific.thomson.com/> ________________________________ From: daisy-bounces-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org [mailto:daisy-bounces-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org] On Behalf Of Manoj Yadav Sent: Tuesday, June 10, 2008 11:00 AM To: daisy-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org Subject: [daisy] Navigation tree problems Hi Is it possible to display different navigation trees for different users. Actually I have separate branches created for each group of users. My requirement is that for each user the navigation tree should show the documents of the branch to which that particular user has access to and should not show any documents he is not allowed access to. -- Thanks & Regards Manoj My Corporation ________________________________________ _______ daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org list information: http://lists.cocoondev.org/mailman/listinfo/daisy -- Thanks & Regards Manoj My Corporation
Post Follow-up to this message Re: Navigation tree problemsHi Thanks for the response So If I have only one site and follow your method creating collections and restricting access. Then granting access on the user account basis for the each collection would I be able to access the welcom to site page and the navigation tree. I am not able to do that with branches presently. I have only one site. On Tue, Jun 10, 2008 at 10:21 PM, <zachary.mentz-qs4m+OjfQoH+fug3k4jHmNBPR1l H4CV8@public.gmane.org> wrote: > I think I understand. > > > > This is an ACL issue. ACL is evaluated from top down. If there's > conflicting statements, whichever one is on bottom will win. Also, any > statements that restrict the role of "administrator" aren't going to work > since administrators always have full rights. You said you're using a > different role, cosite_admin, so I think you're fine there, but just to be > clear. > > > > I've done something similar with our own instance of Daisy, but instead of > restricting based on branch, I restricted by collection. > > > > My first statement looks like this: > > > > If true then everyone > > Read Live(X) Read(X) Write(X) Delete(X) Publish(X). > > > > This shuts off all sites to all viewers except admins. My next line opens > up one site to one role, it looks like this: > > > > If collections = 2 then > > Role: product_management > > Read Live(check) Read(check) Write(check) Delete(check) Publish(check) > > > > So now anyone in the product_management role should be able to log in and > see only the site that is part of collection 2. And just repeating > statements like this downward with different collections and roles gives m e > something similar to what I think you're looking for. > > > > I think you might find it easier (if you're not doing so already) to break > those things up into different sites and collections instead of querying o n > branches. That'll give you freedom to add one document to several > collections if you ever decide you want to share certain documents between > roles (and you wouldn't have to edit the ACL). Just a thought. > > > > > > *Zack Mentz* > Technical Document Analyst > Liquent > > *Thomson Scientific* > > > zachary.mentz-L+G57L1VLRZBDgjK7y7TUQ@public.gmane.org > www.liquent.com > http://scientific.thomson.com > ------------------------------ > > *From:* daisy-bounces-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org [m ailto: > daisy-bounces-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org] *On Behal f Of *Manoj Yadav > *Sent:* Tuesday, June 10, 2008 12:10 PM > *To:* Daisy: open source CMS - general mailinglist > *Subject:* Re: [daisy] Navigation tree problems > > > > Hi > > The problem I am facing is that I have configured say 5 branches. Now I am > creating an administrator for each of these branches. In the navigation tr ee > I have links to 5 documents that query daisy for that particular branch on > display the results on a page. Now my requirement is that each administrat or > should not be able to see the links of the other 4 documents in the > navigation tree and should only see the link of the document that display s > the contents of this branch. > > Now using ACL I configured a role cosite_admin and for this role I revoked > all the permissions including the read permission for all the doucments. > Then I created another rule saying that if a user admin1 belonging to rol e > cosite_admin role is there then I granted him complete access to his branc h > for e.g. branch1 > > The problem is since I revoked all the rights on all the pages except his > branch , after logging in using the admin1 id I get the message No sites a re > available to you . In other words the sites welcome page is no longer > accessible for this user. So nothing comes up in the navigation tree as we ll > so the navigation tree is not accessible either . > > > > On Tue, Jun 10, 2008 at 8:42 PM, <zachary.mentz-qs4m+OjfQoH+fug3k4jHmNBPR 1lH4CV8@public.gmane.org> > wrote: > > What didn't work about setting that through the ACL, Manoj? > > > > *Zack Mentz* > Technical Document Analyst > Liquent > > *Thomson Scientific* > > > zachary.mentz-L+G57L1VLRZBDgjK7y7TUQ@public.gmane.org > www.liquent.com > http://scientific.thomson.com > ------------------------------ > > *From:* daisy-bounces-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org [m ailto: > daisy-bounces-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org] *On Behal f Of *Manoj Yadav > *Sent:* Tuesday, June 10, 2008 11:00 AM > *To:* daisy-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org > *Subject:* [daisy] Navigation tree problems > > > > Hi > > Is it possible to display different navigation trees for different users. > Actually I have separate branches created for each group of users. > My requirement is that for each user the navigation tree should show the > documents of the branch to which that particular user has access to and > should not show any documents he is not allowed access to. > > > -- > Thanks & Regards > > Manoj > > My Corporation > > > ________________________________________ _______ > daisy community mailing list > Professional Daisy support: > http://outerthought.org/en/services/daisy/support.html > mail to: daisy-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > > > > > -- > Thanks & Regards > > Manoj > > My Corporation > > ________________________________________ _______ > daisy community mailing list > Professional Daisy support: > http://outerthought.org/en/services/daisy/support.html > mail to: daisy-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > > -- Thanks & Regards Manoj My Corporation
Post Follow-up to this message RE: Navigation tree problemsYes, you can do it that way. What you'd need to do is create the collections first, then edit your home and navigation page to be included in all the collections... i.e. edit the document, go to the misc tab and select all of the collections. In the navigation document, you'll also need to click on the root node and assign that to all collections so that all the pages can show up in the navigation (although the ACL will filter out the ones the user doesn't have access to). Only the home and navigation would need to be in all collections. That ACL should still work. I find it easier to work between sites. I use one site = one collection. It's just clearer for me and gives me the ability to change skins and such from one collection to the next... but if you're not concerned about that, then you can do it this way. Zack Mentz From: daisy-bounces-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org [mailto:daisy-bounces-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org] On Behalf Of Manoj Yadav Sent: Tuesday, June 10, 2008 1:00 PM To: Daisy: open source CMS - general mailinglist Subject: Re: [daisy] Navigation tree problems Hi Thanks for the response So If I have only one site and follow your method creating collections and restricting access. Then granting access on the user account basis for the each collection would I be able to access the welcom to site page and the navigation tree. I am not able to do that with branches presently. I have only one site. On Tue, Jun 10, 2008 at 10:21 PM, <zachary.mentz-qs4m+OjfQoH+fug3k4jHmNBPR1l H4CV8@public.gmane.org> wrote: I think I understand. This is an ACL issue. ACL is evaluated from top down. If there's conflicting statements, whichever one is on bottom will win. Also, any statements that restrict the role of "administrator" aren't going to work since administrators always have full rights. You said you're using a different role, cosite_admin, so I think you're fine there, but just to be clear. I've done something similar with our own instance of Daisy, but instead of restricting based on branch, I restricted by collection. My first statement looks like this: If true then everyone Read Live(X) Read(X) Write(X) Delete(X) Publish(X). This shuts off all sites to all viewers except admins. My next line opens up one site to one role, it looks like this: If collections = 2 then Role: product_management Read Live(check) Read(check) Write(check) Delete(check) Publish(check) So now anyone in the product_management role should be able to log in and see only the site that is part of collection 2. And just repeating statements like this downward with different collections and roles gives me something similar to what I think you're looking for. I think you might find it easier (if you're not doing so already) to break those things up into different sites and collections instead of querying on branches. That'll give you freedom to add one document to several collections if you ever decide you want to share certain documents between roles (and you wouldn't have to edit the ACL). Just a thought. Zack Mentz Technical Document Analyst Liquent Thomson Scientific zachary.mentz-L+G57L1VLRZBDgjK7y7TUQ@public.gmane.org www.liquent.com <http://www.liquent.com/> http://scientific.thomson.com <http://scientific.thomson.com/> ________________________________ From: daisy-bounces-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org [mailto:daisy-bounces-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org] On Behalf Of Manoj Yadav Sent: Tuesday, June 10, 2008 12:10 PM To: Daisy: open source CMS - general mailinglist Subject: Re: [daisy] Navigation tree problems Hi The problem I am facing is that I have configured say 5 branches. Now I am creating an administrator for each of these branches. In the navigation tree I have links to 5 documents that query daisy for that particular branch on display the results on a page. Now my requirement is that each administrator should not be able to see the links of the other 4 documents in the navigation tree and should only see the link of the document that displays the contents of this branch. Now using ACL I configured a role cosite_admin and for this role I revoked all the permissions including the read permission for all the doucments. Then I created another rule saying that if a user admin1 belonging to role cosite_admin role is there then I granted him complete access to his branch for e.g. branch1 The problem is since I revoked all the rights on all the pages except his branch , after logging in using the admin1 id I get the message No sites are available to you . In other words the sites welcome page is no longer accessible for this user. So nothing comes up in the navigation tree as well so the navigation tree is not accessible either . On Tue, Jun 10, 2008 at 8:42 PM, <zachary.mentz-qs4m+OjfQoH+fug3k4jHmNBPR1lH 4CV8@public.gmane.org> wrote: What didn't work about setting that through the ACL, Manoj? Zack Mentz Technical Document Analyst Liquent Thomson Scientific zachary.mentz-L+G57L1VLRZBDgjK7y7TUQ@public.gmane.org www.liquent.com <http://www.liquent.com/> http://scientific.thomson.com <http://scientific.thomson.com/> ________________________________ From: daisy-bounces-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org [mailto:daisy-bounces-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org] On Behalf Of Manoj Yadav Sent: Tuesday, June 10, 2008 11:00 AM To: daisy-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org Subject: [daisy] Navigation tree problems Hi Is it possible to display different navigation trees for different users. Actually I have separate branches created for each group of users. My requirement is that for each user the navigation tree should show the documents of the branch to which that particular user has access to and should not show any documents he is not allowed access to. -- Thanks & Regards Manoj My Corporation ________________________________________ _______ daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org list information: http://lists.cocoondev.org/mailman/listinfo/daisy -- Thanks & Regards Manoj My Corporation ________________________________________ _______ daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org list information: http://lists.cocoondev.org/mailman/listinfo/daisy -- Thanks & Regards Manoj My Corporation
Post Follow-up to this message
Sponsored Links
Show a Printable Version
Email This Page to Someone!
Receive updates to this thread
Powered by vBulletin
Copyright 2000-2006 Jelsoft Enterprises Limited.
