I've had several problems come up when using user-created feeds (those that have create feeds permission but do not have 'administer nodes' permission). First let me clarify, this is an enhancement request. I'm willing and able to help out, but this issue seems to require eyeballs that have already messed with this code before. I'm basically asking to remove any dependancy on 'administer nodes' access rights for basic functionality.

I've created a new definition of aggregator2_block, which is simply 'my feeds' - a list of 'my own' submitted feeds. This was easy. Making it work is still problematic. Mostly this seems to revolve around the aggregator2-feed node. Without administer node access, all kinds of undesired things happen and the feed is basically unuseable. The settings which are at the root of the problem are the expiration time and promotion/publish behaviour. Without node administration access these do not get set. The defaults when they are not set result in expiration of articles immediately, all items (including the feed itself) being promoted to front page (not what I desired), and I believe that they are not getting the publish bit set which also is expiring them immediately.

To duplicate, create a feed without 'administer nodes' rights and try to populate it.

I've been having a devil of a time troubleshooting this because it seems that no matter what I patch, something else is expiring all the articles on refresh. Basically a person with rights to create a feed can do so, but if it is refreshed it will end up with 0 items because of other 'node admin' factors kicking in. If I comment out the expiration entirely, I can get the feed to refresh and have contents, but everybody's feeds get on the front page. Not horrible, but it wasn't my desire. Of course not being able to expire will have its own set of problems over time...