RSS Import Options for Evolution CMS Projects

RSS import can save time, but only if you control how imported content maps into documents, fields, and publication rules.

This donor started from a simple request for an RSS import snippet, but the real project question is broader: how should imported feed content enter an Evolution CMS site?

What to Decide Before You Import

Will feed items become resources, records in a custom table, or cached external content?
How often should imports run?
How will duplicates be detected?
Which fields should be trusted from the feed and which should be normalized?

On smaller sites a simple RSS import snippet can be enough. On larger projects, imports should behave more like scheduled synchronization jobs with clear mapping rules.

Newer post

Building a jQuery Accordion Menu That Remembers Its State

A simple accordion menu becomes much easier to use when it remembers which branches were opened and highlights the current page.

Older post

Throttling TXNewsletters with Cron and Send Limits

How to avoid hourly mail limits by moving newsletter delivery into controlled batches instead of sending everything at once.