Multiple feed fixes and enhancements

[peaceablewhale]

Currently, the feed always returns the same subtitle, self link, alternate link and replies link no matter what the page type is. I think they should be different for each page type.

Initial attempt to add those features to feed-atom.php

Initial attempt to add new functions to link-template.php

get_day_feed_link and get_day_comments_feed_link functions are to be added...

Changes into attached PHP files in one patch file - diff preview

atom:id should be changed as well. This patch replaces the feed-atom.php part of the previous patch.

Thanks simek for the patch. I have uploaded a new patch replacing the feed-atom.php part.

This is the first time for me to generate a patch file. Please let me know if I have done anything wrong. Thanks.

New patch, replaces all old patches.

The v2 patch has included the changes proposed in #9515, the patch will have to be updated when #9515 is settled.

In addition, since I have made many modifications to the files, I would like to get some comments from the core developers.

Could this be added in WordPress 2.8?

patch applies cleanly

This report will be updated after #9515 is fixed.

patch is b0rke

Patch updated.

Version 3 of the patch, changes from #9515 adopted, with minor corrections

Postponing from 2.8.

patch still applies clean

Patch will be updated after #4967 is fixed.

A new patch has been uploaded, with the changes proposed in #4967 excluded. The patch also fixes #9992, #9831 and some formatting issues in feeds.

The updated version 4 patch fixes #4523 as well.

Correction: It's #4253, not #4523

Patch updated to fix a problem that the required <description> element is sometimes not displayed under RSS 2 channel.

Attempt to fix #8828 as well.

Added the change proposed in #10016

Added the changes proposed in #10509, also made Atom support sy:updatePeriod and sy:updateFrequency.

Not to be too picky, but it'd be nice if this was closer to the ​WordPress Coding Standard. Specifically, reversing most comparisons, spacing things out a bit to make them easier to read and avoiding quote-escaping by going between single and double quotes where appropriate.

That being said, after a very quick visual skim over the code it looks like it adds a lot more flexibility and robustness to the feed system of WP, so I'm all for it (haven't tested to see if the patch applies cleanly or does as advertised). Looks very thorough.

feed_link() and feed_entry_link() looked identical (except for the filter they run), perhaps they can just be combined into a more generic feed_link() function, with a parameter indicating what filter to run over the resulting code, or just have it run at the point that calls them?

You're using get_lastpostmodified() to get a value for feed_updated(), but it seems like that value would not necessarily be accurate for anything except the full-site feed. If there's an easy way to get that date from the first matching item in the feed, that seems like that would consistently give you the correct value for that specific feed.

@beaulebens:

Thanks for your comment. I will upload a patch that conforms to the coding standard later.

The refreshed patch is expected to combine feed_link() and feed_entry_link() into generic_feed_link(), with a parameter indicating which filter to be used.

I know that get_lastpostmodified() is problem... but I am not able to fix that until #4575 is fixed...

After a second thought, I think that adding $is_entry to feed_link() is better. A refreshed patch has been uploaded, and it is now closer to the WordPress Coding Standard.

Updated the patch to resolve the conflict caused by [11864].

Updated the patch to resolve the conflict caused by [11980].

Marking this report "needs-testing" in order to gain attention in the upcoming bug hunt.