RSS Feed
SynaptikCMS generates an RSS 2.0 feed automatically at /core/feed.php. No configuration is required — the feed is always available.
As of the v1.3.3 core restructure, the feed moved from /feed.php to /core/feed.php. Unlike contact-process.php, there is no backward-compatible redirect for the old path — update any hardcoded links, bookmarks, or external feed subscriptions to the new URL.
Feed URL
https://yourdomain.com/core/feed.php
The feed lists published articles in reverse-chronological order, capped at the 20 most recent. Pages and Projects are not included.
What the feed contains
Each item in the feed includes:
| Field | Source |
|---|---|
<title> | Article title |
<link> | Full article URL via cleanUrl() |
<guid isPermaLink="true"> | Full article URL (permanent link) |
<pubDate> | Publication date in RFC 2822 format |
<description> | Summary field if set, otherwise a plain-text excerpt (300 chars) |
<category> | One entry for the article's category (if set), plus one entry per tag |
Channel-level metadata (<title>, <description>, <link>, <language>) comes from config.json. The channel also includes a self-referencing <atom:link rel="self"> pointing back to the feed URL, and a <lastBuildDate>.
Auto-discovery
The feed <link> tag is injected automatically into <head> by render_header_scripts() — themes do not need to add it manually:
<link rel="alternate" type="application/rss+xml"
title="Site Name" href="https://yourdomain.com/core/feed.php">
Limiting the number of items
The feed is hard-capped at 20 articles — there is no setting to change this from the admin panel. To adjust it, edit the array_slice(...) call in core/feed.php directly.
Caching
The feed does not set an explicit Cache-Control header itself. The root .htaccess applies ExpiresByType application/xml "access plus 0 seconds", which tells caches to treat the response as immediately stale — in practice equivalent to no caching, though not the same directive as an explicit Cache-Control: no-store. If you want server-side caching instead, wrap the output in a file-based cache keyed to the most recent article's last_modified timestamp.