EP RSS

EP RSS adds RSS 2.0 and Atom 1.0 feed generation to PageMotor. Visitors and feed readers (Feedly, Inoreader, NetNewsWire) can subscribe to your content. Search engines also consume feeds for faster indexing.

Published by ElmsPark Studio.

Overview

• RSS 2.0 at /feed/ (conventional URL).
• Atom 1.0 at /atom/.
• Configurable content filter: posts only, pages only, specific categories, or custom queries.
• Per-feed customisation: title, description, image.
• Summary or full content per feed.
• Valid markup passes the W3C Feed Validator.

Requirements

• PageMotor 0.8.2b or later
• EP Suite base class

Installation

1. Download ep-rss.zip from the EP Suite downloads page.
2. Upload via Plugins → Manage Plugins. Activate.
3. Open https://yoursite.com/feed/ — should render a valid RSS feed of your latest content.

Settings

• Feed title. Usually your site name.
• Feed description. Short site description.
• Feed image. Square logo.
• Content filter. All pages, specific category, or custom.
• Summary vs full. Show post excerpts or the full body. Full content is friendlier to readers; summary drives clicks back to your site.
• Items per feed. Typically 10-20.
• Include images. Embed images in the feed content.

Auto-discovery

The plugin adds <link rel="alternate"> tags to your site’s head, so browsers and feed readers auto-detect the feed URL. Most readers can subscribe by just pasting your homepage URL.

Multiple feeds

Configure additional feeds under Custom feeds:

• URL path (e.g. /blog-feed/).
• Title, description.
• Query: which content to include (specific category, tag, etc.).

Useful when you want a separate feed for a blog category, a newsletter archive, or a podcast.

Troubleshooting

“/feed/ returns a 404”

PageMotor’s router needs to recognise the feed URL. Check the plugin is active. Also check you don’t have a page at the path /feed/ that’s taking precedence.

“Feed validates but my reader doesn’t update”

Feed readers poll on their own schedule (usually every hour). Adding content doesn’t instantly appear in the reader. Wait.

“Items per feed setting isn’t respected”

Double-check the setting saved. Also check your reader isn’t pulling from a cached URL with different parameters.

“Images in the feed don’t load”

Check the image URLs are absolute (include https://yoursite.com/). Relative URLs in feed content don’t resolve in most readers.

Feedback and corrections

For a quick question about this plugin, EP Support inside your admin is the fastest option. The chat widget sits on every EP plugin settings page and knows which one you’re on, with starter questions and links preloaded for that exact screen.

For anything bigger — a bug report, a feature request, or a “how do I…” that needs a real reply — open a ticket at help.elmspark.com. A real person, helped by AI, writes the reply. Usually within a few hours. Tickets don’t disappear into the void.

Changelog

1.1.10

• Settings language menu. The language menu in this plugin’s settings now lists only the languages it is actually translated into, plus English, so you can no longer pick a language that changes nothing.

1.1.9

• Stops privately-marked pages appearing in your feed. The previous release fixed this for whole content types that are marked private. It did not cover a page you protect one at a time, which is how EP Private Access works: your feed could carry that page’s title, its opening text and its address, while the page itself still asked the visitor to sign in. If you protect individual pages, treat anything that appeared in your feed before this release as having been public.
• Every item is now offered to your other plugins before it goes out, so a plugin that protects a page can keep that page out of the feed. Protecting pages one at a time needs EP Private Access 1.0.6 or later.
• Turning a protection plugin on or off now takes effect straight away. Feeds are cached for up to an hour, and the cached copy used to outlive that change. It no longer does.
• Nothing else changed. A site with no protection plugin produces exactly the feed it did before.

1.1.8

• Stops protected content appearing in your feed. Members-only pages were being published to anyone who asked for the feed: the title and excerpt at /feed, and the full text where the feed is set to include it. A feed for a single content type served that entire protected type on request. If you use EP Membership or any plugin with protected content, treat anything published before this release as having been public.
• Every item is now checked against the same permission the page itself uses, as an anonymous reader would see it. A feed address carries no sign-in, so the anonymous view is the only correct one.
• Feeds are now produced later in the page cycle, which is what makes that check possible. Your feed addresses are unchanged.
• A welcome side effect of that change: content types added by other plugins, such as blog posts, events and locations, now appear in the main /feed. They were silently missing before.