Hi, I'm using a blog for a use it's not intended for, where users can submit frontend blog posts, and have the option of restricting their access to "private" or "public".
Private = members of a specific member group
Public = not members of that member group, but still authenticated users, as the blog is still protected.
I have added a makePrivate true/false to my BlogPost type, and have this getting set properly on my front end submission form, however, I wondering what it should do to make it actually so something?
Option 1 - add member group picker to the Blog Type, and use this to add "Access" rules programatically to the private posts when my submit form created them... I think I would then have to modify the xslt for the BlogListPosts etc to check umbraco.library.hasaccess for each post? (This xslt would arguably be a useful submission to the core blog code anyway?)
Option 2 - modify the xslt to take account of the makePrivate flag and the current logged on member's group? (Which I'm not sure how to do it xslt, but it can't be too hard).
Can anyone think of any other options that might be easier, and would option 1 be useful to anyone else?
Is it likely that either of these will be inefficient and are thus totally stupid ideas?
protecting certain posts
Hi, I'm using a blog for a use it's not intended for, where users can submit frontend blog posts, and have the option of restricting their access to "private" or "public".
Private = members of a specific member group
Public = not members of that member group, but still authenticated users, as the blog is still protected.
I have added a makePrivate true/false to my BlogPost type, and have this getting set properly on my front end submission form, however, I wondering what it should do to make it actually so something?
Option 1 - add member group picker to the Blog Type, and use this to add "Access" rules programatically to the private posts when my submit form created them... I think I would then have to modify the xslt for the BlogListPosts etc to check umbraco.library.hasaccess for each post? (This xslt would arguably be a useful submission to the core blog code anyway?)
Option 2 - modify the xslt to take account of the makePrivate flag and the current logged on member's group? (Which I'm not sure how to do it xslt, but it can't be too hard).
Can anyone think of any other options that might be easier, and would option 1 be useful to anyone else?
Is it likely that either of these will be inefficient and are thus totally stupid ideas?
Thanks,
Chris
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.