Many users give aliases to nodes with the path module and the pathauto module. That is what users see in the URL bar. However /crss/alias does not work to get the RSS feed for the node aliased by the comment, so there is no clean way to tel users, "If you want the rss feed for this node, just insert /crss in front of the path."

If you mapped /crss/alias to the actual target, then this would work. Thanks for this module, though.

Comments

gnassar’s picture

+1 -- that's a great point.

I suppose also appropriate is the format of the URL in the first place; as standard feeds are basically /feed arguments off of pages, it would seem that the proper URL for a content node would probably be sample.com/(node path)/crss, not sample.com/crss/(node path).

tangent’s picture

I agree. The convention for node feeds seems to be something like "taxonomy/term/1/feed" or "view/feed" so using something like "view/comments/feed" (I dislike the "crss" name because it is not obvious) seems to better follow this convention than the current method.

I started doing some work on that but didn't create a patch yet. I can if this convention is preferred.

As far as supporting URL aliases, this module will support aliases for its own feeds. Supporting aliases of node feeds and providing a comment feed at that same alias is another trickier matter. It's easier, and more desirable, to simply follow the convention for the default feed urls.

sillygwailo’s picture

If I'm reading what tangent and others say correctly, he (or we) would like to be able to specify in the Pathauto settings what the feed aliases automatically get set to. Is there a way to incorporate the 'submit' operation of the nodeapi hook? Or to plug into Pathauto's new requirement for the Token module?

David Latapie’s picture

Using alias from Path(auto) would also ensure consistency when moving from one database to another, a major concern for me.

lomz’s picture

I would like it to be /node-title-from-path(auto)/feed/ like it is in wordpress.

Gábor Hojtsy’s picture

I agree that the crss prefixed paths are not obvious, but when we add the links to the RSS feeds right into the node pages, I don't see a reason that you would need to tell people to hack URLs, when they can just copy the RSS feed URL their browser recognized. All browsers are now recognizing these feeds.

To have nicer paths, we need a migration plan so that those upgrading would find their old paths working still. Plugging into pathauto might also be an option to let you configure alias schemes on the pathauto screen for comment rss feeds.

lomz’s picture

actually such a plan is not needed, it is already included in path/pathauto

Dave Reid’s picture

Status: Active » Closed (won't fix)

This is a won't fix then.