WordPress plugin intelligence profile

River Embed for FeedLand

Show a FeedLand river — a constantly-updated stream of news from the feeds a FeedLand user subscribes to — on a WordPress page or post.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.1
Current version1.0.0
WordPress coverageTested up to WordPress 7.1
Minimum stackWP 6.1 · PHP 7.4
Directory statusactive
Last directory update14 Sept 20261mo ago
Active installationsNewAdoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records River Embed for FeedLand version 1.0.0 as active, updated 1mo ago and tested up to WordPress 7.1.

Overview

About this plugin

Fetches the river JSON from FeedLand’s API server-side (cached), renders it with its own template, and embeds the result in an isolated iframe. No FeedLand front-end scripts are involved, and no third-party stylesheets, fonts or scripts are loaded — the webfont and item icons ship with the plugin.

Add the river anywhere with the [feedland-rivers] shortcode.

What it talks to

  • Your configured FeedLand server, server-side only, for the river JSON and feed titles.
  • Your configured Template URL, if you set one, server-side only — fetched once and cached, to build the page shell. Leave it blank to use the plugin’s built-in template instead.

-

DuckDuckGo’s icon service, from the visitor’s browser, for each feed’s favicon — sends only the feed’s own homepage URL, on every page view, no cookies or personal data. Privacy Policy / Terms of Service. This can be turned off:

add_filter( ‘feedland_rivers_favicon_url’, ‘__return_empty_string’ );

-

Your configured FeedLand server’s homepage, server-side only, once a day — reads its advertised WebSocket address so live updates (below) reach the right host even on a self-hosted instance whose socket runs on a different subdomain than its API. Falls back to guessing from the server’s own host if this can’t be read.

-

A FeedLand WebSocket address (usually, but not always, the same host as your configured server — see above), from the visitor’s browser, while polling (below) is enabled — listens for FeedLand’s live new-item/updated-item notifications so a poll can be triggered immediately instead of waiting for the next timed check. Nothing from this connection is ever rendered; it’s only compared against the feed URLs already shown before deciding whether to poll early.

Set feedland_rivers_live_updates_enabled to __return_false to turn this off and rely on timed polling alone:

add_filter( ‘feedland_rivers_live_updates_enabled’, ‘__return_false’ );

-

This site’s own REST API (not a third party), from the visitor’s browser, every few minutes — checks for fresh river content and updates it in place without a full page reload. Each request carries a token proving the specific river shown was actually configured on this site, generated when the page itself was rendered; requests for any other username/category/server are rejected. Set feedland_rivers_poll_interval to 0 to turn this off entirely and fall back to only refreshing on a full page reload.

Filters

  • feedland_rivers_max_items — total item cap across all sections (default 20).
  • feedland_rivers_cache_ttl — how long a fetched river stays cached, in seconds (default 180).
  • feedland_rivers_poll_interval — how often the browser checks for fresh content and updates the river in place, in seconds (default 180, 0 disables). Kept equal to feedland_rivers_cache_ttl by default: polling faster than the river cache expires mostly just adds requests that land on cache hits, without showing anything sooner.
  • feedland_rivers_feed_list_cache_ttl — how long the subscribed-feeds list used to filter live updates stays cached, in seconds (default 1800).
  • feedland_rivers_live_updates_enabled — whether the browser opens a WebSocket connection to trigger an early poll on a live update (default true).
  • feedland_rivers_live_updates_socket_url — the WebSocket address to connect to for a given server, or override it if the server’s own homepage doesn’t advertise the right one.
  • feedland_rivers_socket_discovery_cache_ttl — how long a discovered WebSocket address stays cached, in seconds (default 86400).
  • feedland_rivers_favicon_url — the favicon URL for a feed, or ” for none.
WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • feedland
  • feeds
  • news
  • river
  • rss
Compatibility & maintenance

Compatibility & maintenance

Tested with WP 7.1

Marked as tested with the current WordPress 7.1 release.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.1
Minimum requirementsWordPress 6.1 · PHP 7.4
Update activity14 Sept 20261mo ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.