In the last days a new type of RSS Feed was announced: https://jsonfeed.org/
I’m a big fan of JSON an decided to add a JSON Feed in my own site and publish the code as a plugin on Github.
Mhmm… my feed seems to work (I can see the feed entries when I access the url), but when I subscribe to my feed (via Feedbin), the feed is empty. Is this a error within Feedbin or with your plugin?
Update: I just added the feed url directly into the json_feed.php. I know thats probably not correct, but at least “feed_url” is now filled correctly. My JSON feed seems to work in Newsblur right now. But its still not working in Feedbin. So now its more likely an error on Feedbin site (IMHO its a caching issue - they still deliver the corrupt feed, even when I resubscribe to the feed). I currently try to contact them.
@stefanzweifel Yeap, it was a bug within Feedbin - which is now fixed.
During the test, I’ve found another glitch: Feedbin requires the “date_published” entry. Otherwise all entries are displayed with the time Feedbin was catching the feed/article. Currently there is only the “date_modified” key inside the feed. It would be great if you would add the “date_published” key to the feed
Update: As I recognized, that “date_modified” already contained the publish date (instead of the the last update date), I just changed “date_modified” to “date_published” inside the “json-feed.php”.
So, IMHO there is just a solution needed, for the “date_modified” key (as it currently contains the publish date).
Thanks! Is there any way to write the real (last) modified date into the “date_modified” key? Currently it seems that both keys contain the publish date?!
The Plugin currently just uses the “date” field (Link https://github.com/stefanzweifel/kirby-json-feed/blob/master/json-feed.php#L30-L31).
Kirby doesn’t have the concept of “published date” and “modified date” by
default. You could however add a new field called “date_modified” in your
blueprints, set it in your pages and adjust the json-feed plugin.
The plugin code should be simple enough so everyone can add or remove the
fields he or she wants. If the JSON feed would get a lot of traction I
would add all remaining fields. But currently I think thats an overkill.
Okay, accepted! IHMO that key is not that necessary (at least for me), as most feed readers track updated feeds / articles themselves. So I live without the “date_modified” key for now