cr0ybot / feed-block Goto Github PK

Add transforms for content to summary and vice versa. Are there any other feed item blocks that could be swappable?

• Content <-> Summary
• Other?

Firstly, what a fantastic plugin, thank you. I have been looking for something to replace the limited RSS block as I wanted to pull some content from my sites together into one place. Yours is the best RSS plugin I've found and I've tried almost every plugin in the directory. A couple of minor feature requests if I may:

1. The ability to have the images link to the site URL, not the url of the image file.

2. The ability to truncate content to either a set number of words, sentences or the first HTML paragraph.

Thanks again for your efforts.

Like the image block, text-based blocks should also include a placeholder text option. This will also allow me to add block previews and better handle empty feed content.

Currently, the image block by default pulls the first img tag from the description or the contents of a custom tag, but this assumes the tag contents are HTML. There is a setting to use the content itself as the URL, but in the case of podcast feeds, the image URL is provided by an href attribute on the itunes:image tag. Perhaps part of the standard image detection should include checking for itunes:image.

• Check for itunes:image tag as default image (handled in #3)
• Get image URL from custom tag attributes (requires serious rewrite)

The contents of the No Results block are always shown on the front end. Even when empty, <p></p> is rendered.

Silly me, I forgot to hook up the render template.

Reported by @philhoyt

When referencing core blocks, obviously they would use context variables with no namespace, but a plugin should namespace their context vars.

Add feed-block/ to all contexts provided and consumed in the plugin.

The core RSS block prevents pulling in a feed with the same URL as the current site. I think this is probably wise, but I'd like to offer a filter to allow it for some advanced usage that I might not fully grasp at this point.

This should probably be handled by the FeedBlock\Feed\get_feed function so that it can be filtered once in PHP. Will have to consider what kind of return value (WP_Error?) would make the most sense and how that is handled both in editor and front end.

One block for custom namespaced tags with every conceivable formatting option is, in hindsight, really dumb.

Instead, each feed item block—title, summary, image, etc—should include an option for getting the content from a custom tag instead of the default. Each block can then be considered a specific "format".

Add custom content options to these existing blocks:

• Title
• Summary
• Content
• Image

Create new blocks to handle additional functionality:

• Date / Time
• Link