Opened 4 years ago

Last modified 3 years ago

#8828 new enhancement

Tags and Categories are undifferentiable in Atom and RSS feeds

Reported by: znarfor Owned by:
Priority: normal Milestone: Future Release
Component: Feeds Version: 2.7
Severity: normal Keywords: has-patch needs-review
Cc: znarf@…

Description

In RSS feeds this can be achieved using the 'domain' attributes of the category element. This is already done in Wordpress export through the wxr_post_taxonomy function, so we just have to do the same in RSS feeds.

In Atom feeds this can be achieved using the 'scheme' attributes of the category element. The Atom standard is not explicit about what to put in this scheme attributes. There is an interesting topic on Edward O’Connor blog. In my proposed patch, i decided to use the 1st representation and i also considered seriously the 2nd.

In the patch, i'm also adding the 'label' attribute to the atom category element and changed the 'term' attribute to be the tag slug. Seems this are currently the best practices in the Atom community.

Attachments (2)

wp-feed-category.diff (2.1 KB) - added by znarfor 4 years ago.
i tried to not modify too much the function to improve the patch readability, but i think this function can be refactorised somehow after.
wp-feed-category-2.diff (2.3 KB) - added by znarfor 4 years ago.
update of my previous patch

Download all attachments as: .zip

Change History (9)

znarfor4 years ago

i tried to not modify too much the function to improve the patch readability, but i think this function can be refactorised somehow after.

  • Keywords has-patch added

#9236 attempts to fix the same issue.

  • Keywords needs-patch added; has-patch removed
  • Milestone changed from 2.8 to Future Release

broken patch

  • Component changed from General to Feeds
  • Owner anonymous deleted
  • Keywords needs-patch removed

This report will be fixed if the patch from #9510 is accepted.

znarfor4 years ago

update of my previous patch

  • Cc znarf@… added
  • Keywords has-patch needs-review added
  • Milestone changed from Future Release to 2.9

The patch had been updated for 2.9-rare (trunk).

  • Milestone changed from 2.9 to Future Release

Lack of community testing on new patch > punting due to being in beta.

Note: See TracTickets for help on using tickets.