Publish Feeds per role
rhache - May 4, 2008 - 19:18
| Project: | Feed Path Publisher |
| Version: | 5.x-1.1 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Robbie Sternenberg |
| Status: | closed |
Jump to:
Description
To whom it may concern,
Lovely little module. Thanks for the contribution.
I was wondering if you had any intentions of potentially adding a feature that would allow you to specify for which role the feeds would be published (like blocks)?
Probably an odd request, but it would be very useful on some of the sites that I use where the content is visible on a per-role basis.
Thanks,
Rene
#1
Rene:
Thanks for the suggestion. However, truly restricting access per role will be near impossible. While it's possible to restrict the display of feed paths in a document's , we can't prevent users from accessing the feeds once they know the path. Feeds are fundamentally intended to be public so that users can subscribe to them using a variety of readers and aggregators; requiring authentication to access a private feed won't work in many of these applications. Technical concerns and roadblocks aside, creating a framework to handle user authentication for restricted (private) feeds is a complicated issue outside of the scope of this module.
That said, are you asking for a way to *fully* restrict access to some feeds, or do you simply want to hide the display of the paths in the document's (knowing that anybody who knows the direct path can still access the feed)?
#2
Sorry -- accidentally set this issue to "won't fix" prematurely.
#3
Todd,
I agree that full access control/authentication is outside the scope of this module.
All I want is the path to NOT be added to the document head on a per role basis.
I'm aware of the limitations, but I can take care of the "actual" authentication's by some other means.
Thanks,
Rene
#4
Rene:
Okay, sounds good. I'll add this request to the project's roadmap.
#5
Assigning the issue to myself.
#6
Assigning to self.
#7
This has been added to the Drupal 5.x-1.4 release. Working on a Drupal 6 port now.
#8
Automatically closed -- issue fixed for two weeks with no activity.