You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even it is not referenced in the sites html, the default feed for events at example.org/event/feed returns
all published events, regardless of their event timing
ordered by publication date
https://gatherpress.org/events/feed (in opposite to the before mentioned,) returns all comments AND RSVPs colorfully mixed which makes it almost completely useless.
One can be lucky, when the event-date block is still at the top of the content, so its gets shown in the auto generated excerpt. But this depends on editors choice, if the first five blocks were paragraph blocks, this would just be a regular excerpt.
Designs
The rendered feed content for events could be improved by:
only listing upcoming events
ordered by start date & time
filtering the_excerpt_rss to return event dates & venue, and append an excerpt, if one was explicitly set
The feed for comments and RSVPs should be separated into two.
Is your enhancement related to a problem? Please describe.
Currently events use the absolute default for their rendered output, which results in weird feed data.
Even it is not referenced in the sites html, the default feed for events at
example.org/event/feed
returnshttps://gatherpress.org/events/feed
(in opposite to the before mentioned,) returns all comments AND RSVPs colorfully mixed which makes it almost completely useless.One can be lucky, when the event-date block is still at the top of the content, so its gets shown in the auto generated excerpt. But this depends on editors choice, if the first five blocks were paragraph blocks, this would just be a regular excerpt.
Designs
The rendered feed content for events could be improved by:
the_excerpt_rss
to return event dates & venue, and append an excerpt, if one was explicitly setThe feed for comments and RSVPs should be separated into two.
Resources
Describe alternatives you've considered
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: