How to Guides

These guides assume pkg_rca_feedfactory is installed, core plugins are enabled, and you understand Import2Content saves require a manual fetch test before cron trust.

Partner RSS into your homepage blog category

Add the partner feed URL in Components, RCA Feed Factory, map Import2Content to your news category, choose publish on import or unpublished for editor review, and schedule hourly or daily fetch. Point a blog menu item at that category. You know it worked when new remote items appear as Joomla articles without manual paste on the schedule you set.

Editor approval before syndicated posts go live

Set Import2Content publish state to unpublished or equivalent draft setting, fetch on schedule, and let editors publish from Content, Articles. You know it worked when new items land unpublished in the right category and never hit the live blog until someone publishes them.

Podcast or video enclosures into Helix blog layouts

Configure enclosure mapping in Import2Content, use Feed Factory 6.0.18 or newer so the Helix Format fieldset appears, install RCA Helix Compat with Helix Format On and Apply Helix blog format for that feed, and leave Media Bridge On when Helix and core disagree on featured and intro images. Confirm format switches and image switches separately because they fix different problems.

Migrate from RSS Factory Pro to Joomla 6

Work on staging with backup, install RCA pkg_rca_feedfactory, read UPGRADE and CREDITS docs, verify feeds and Import2Content rules, manual fetch and compare counts and quality to the old site, point Pro updater at private Pro feed, then cut over production and enable cron. You know it worked when fetch succeeds, Magpie fatals are gone, mapping matches expectations, and updater sees RCA feed.

Multiple partner feeds under one navigation hub

Create one feed record per source, use separate categories or a shared category with clear titles, stagger schedules if sources are large, and publish mod_rca_feedfactory or mod_rca_feedfactory_categories where the template needs navigation. You know it worked when each source imports cleanly without colliding rules and editors can tell which category owns which source.

Tune Import2Content after a bad first fetch

Fix field maps and category, save the feed record, manual fetch once, inspect one new article and one updated article, then adjust cron only after manual behavior looks correct. Turning cron up while maps are wrong just automates embarrassment.