Atom and RSS2 feed issues in 1.1.10 and 2.0

[Red G. Brown]

Items that are modified, but are not new, are being moved to the "newest" position in the feeds. In 1.1.10, I've only been able to get it to occur in the Atom feed. I just tested it on this site, which is running 2.0, and it occurs for both feed types.

In both 1.1.10 and 2.0, the Atom feed does not validate, with more errors being produced by 2.0 than 1.1.10. Here's my modification time tests on this forum:

http://www.simplemachines.org/community/index.php?action=.xml;sa=news;type=atom;limit=10;boards=7

http://www.simplemachines.org/community/index.php?action=.xml;sa=news;type=rss2;limit=10;boards=7

and here's the validation tests:

http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fwww.simplemachines.org%2Fcommunity%2Findex.php%3Faction%3D.xml%3Bsa%3Dnews%3Btype%3Datom%3Blimit%3D10%3Bboards%3D7

http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fwww.simplemachines.org%2Fcommunity%2Findex.php%3Faction%3D.xml%3Bsa%3Dnews%3Btype%3Drss2%3Blimit%3D10%3Bboards%3D7

Atom does not validate, and RSS2 validates, but gets recommendations for improvement.

[SleePy]

Atom support in SMF is for Atom 1.0 not the newer version I believe that validator is looking for.

[Red G. Brown]

Both feeds have problems that need to be corrected.

[SleePy]

As I said, our Atom feed is for the 1.0 version of Atom.  It isn't broken, it just isn't updated the newest version of Atom.  I consider asking for Atom 2.0 is a feature request.
The other one is just a suggestion, not a bug.

[Red G. Brown]

"Items that are modified, but are not new, are being moved to the "newest" position in the feeds. "

[Arantor]

The content is effectively newer than it was before, isn't it?

Note it also reflects on the 'new' status if someone modifies a post you'd already read; it gets flagged as new again.

[Red G. Brown]

No, it isn't new at all. Posts that are several years old, and posts that get modified over and over again are spamming the RSS feeds. The obvious solution is to give a choice as to what is considered new, but by default, modified posts are in no way new, and should not be forced to spam the feeds. The feeds should only show a post once, and doing it any other way should at best be an option, not a forced imposition.

[Arantor]

I don't mean in the feeds; I mean in the actual messages table. When a post is modified, anyone who has previously read the topic will see it marked as new, because it is content they won't have read.

[Red G. Brown]

Most modifications are correcting typos. Not something I want to get spammed with.

[Red G. Brown]

Actually, now that I think of it, I think editing posts should be barred after a reply has been begun or submitted.

[Arantor]

That would best be an option for the admin (and they can already disable editing entirely, or after a set amount of time) because there are plenty of times you'd go back and edit the opening post for something based on ongoing feedback in the thread.

[Red G. Brown]

The ongoing feedback thing is more of a moderator or admin action, and they typically have the power to do that regardless of what the normal setting is. The point here is to make it so that normally, a post can't be edited after replies have begun. Right now, that's not possible.

[Norv]

Supporting Atom 2.0: http://dev.simplemachines.org/mantis/view.php?id=4053

[Red G. Brown]

Thank you very much Norv, I look forward to when this issue is corrected.