When "Create feed aliases" is checked, pathauto makes aliases of the form node/1/feed. Individual nodes don't have feeds -- this should only apply to taxonomy terms, I believe.

Comments

eferraiuolo’s picture

eferraiuolo commented
Priority: Normal » Critical

I agree and have noticed this also. These node/#/feed alias are also kept for example if the node's path contained its title, and the title of the node changes, the old node/[title]/feed url alias will still be in the table.

example:
In pathauto page nodes are set to the following in admin >> settings >> pathauto:
[catpath]/[titile]

Now say you have a taxonomy term, "news" and you created a new node titled "press release" then pathauto will make the following url aliases:
news/press_release
news/press_release/feed

Now if you were to change the nodes title, to "September press release" for example, and your admin >> settings >> pathauto is set to replace on aliases you will have the following url aliases:
news/september_press_release
news/september_press_release/feed
news/press_release/feed

The old "feed" alias for when the node was titled "press release" will still exist, along with the new "feed" alias for the node's new title. And both of these URL are usless, and the older "feed" alias (news/press_release/feed) has to be deleted by hand.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Assigned: Unassigned » mikeryan
Category: bug » support
Priority: Critical » Normal

Well, this functionality was specifically requested and implemented back in 4.5. I seem to recall at the time that individual nodes had the XML icon and the RSS link in the header, so it seemed to make sense at the time to have those links reflect the alias. Has it outlived its usefulness in 4.6 and later? Does anyone have a need for it now? Maybe the answer is to allow node and taxonomy feeds to be enabled separately...

boris mann’s picture

boris mann commented
Category: support » bug

Individual nodes don't have XML feeds. They never have.

There might be comment feeds at some point, but they wouldn't be attached to the node in any case e.g. subscription/$nid/feed or feed/$nid/feed -- the first would be for a new subscription module, the second would be in the future when feeds are centralized in a feed.module instead of in node.

path.module won't delete the feed....because the feed doesn't/has never existed (unless commentrss contrib module does this? I've never seen it...). So, there will be lots of */feed path aliases hanging around.

I've changed this back to a bug report, because AFAIK, aliases are being created for paths that do not exist, and this should apply only to taxonomy.

And thanks for all the fantastic work on pathauto. I'm hoping some of the path performance optimizations let this into core in the next cycle.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Category: bug » feature

It's still not a bug, the path being aliased does exist (even if it's not particularly useful by default). And it is potentially useful - now that I've become familiar with the relativity module I'm contemplating using it in Fenway Views, when I do I would like to provide a node/<nid>/feed comprising related nodes.

I will make the feed generation separately enablable (?) for nodes and taxonomy.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Status: Active » Fixed

I've committed the enhancement - generation of feed aliases is separably enablable now. Visiting the settings page will update the variables automatically, then you can explicitly disable feed aliases for nodes.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Status: Fixed » Closed (fixed)