Weave Code
Oc Rssfetcher Plugin Laravel Package
vdlp/oc-rssfetcher-plugin
RSS Fetcher plugin for October CMS that retrieves, parses, and displays RSS/Atom feeds using a ready-to-use component. Add feed content to pages and templates, with caching to reduce repeated external requests.
A great October CMS plugin which allows you to fetch RSS items from various sources to put on your website.
Frequently asked questions about Oc Rssfetcher Plugin
- Can I use vdlp/oc-rssfetcher-plugin in a plain Laravel application?
- No. This is an October CMS plugin, not a standalone Laravel package, and it registers a backend UI, models, migrations, and a front-end component that only exist inside October CMS. In a plain Laravel, Livewire, or Inertia app it cannot be installed or used. For those stacks evaluate a generic feed library such as laminas/laminas-feed or willvincent/feeds, or build a thin ingestion service.
- How do I install the RSS Fetcher plugin for October CMS?
- Install it with Composer from the October marketplace or directly from the GitHub repository, then place it in the project plugins path and register the plugin. Run the standard October migrations so the feeds and fetched item tables are created. After that, add the ready-to-use component to your page or template and configure your feed sources.
- Does version 4.0.0 still support October CMS 3.x?
- The 4.0.0 release bumps the major version solely to declare October CMS 4.x compatibility, which strongly implies the 3.x line is no longer the supported target for that branch. The changelog is a single line and does not state dropped 3.x support explicitly. If you are staying on October CMS 3.x, pin 3.3.0 exactly in composer.json and do not float the constraint.
- What PHP, Laravel, and October CMS constraints does version 4.0.0 declare?
- The release notes do not state any PHP, Laravel, or October core constraints, so you must open the composer.json in the 4.0.0 tag and read them directly. Confirm the PHP version, the october core package constraint, and the underlying Laravel version against your target environment. Also check whether it hard-conflicts with October CMS 3.x before upgrading.
- Are there database migrations or schema changes between 3.3.0 and 4.0.0?
- There is no migration guide in the release notes, so schema changes for feeds, fetched items, or fetch logs are unverified. Test the upgrade in staging against a production data snapshot, capture before and after row counts, and confirm that feed definitions and fetched item history survive. Keep a documented rollback path by restoring the database snapshot and reverting composer.lock and the plugin version.
- How do I display fetched RSS items on a page in October CMS?
- The plugin ships a ready-to-use component that retrieves, parses, and renders RSS and Atom feed content. Add the component to your page or template and point it at your configured feed sources. Fetched content is cached to reduce repeated external requests, so review the fetch interval and retention settings. If front-end rendering is exposed, verify Twig and backend component usage on your target platform.
- How should I schedule feed fetching in production?
- Fetching runs through October CMS scheduled and console tasks, so the scheduler must run on the host where the October deployment lives. Configure cron to call schedule:run on that host and confirm it with a representative feed set. If your architecture uses October only for content and a separate Laravel service for processing, the plugin and its scheduler still belong in the October deployment, not in the API or worker deployment.
- Does the plugin depend on other vdlp plugins or on APIs deprecated in October 4?
- Hidden transitive dependencies such as shared vdlp toolbox plugins are not visible in the release notes and must be confirmed before you commit. Check the composer.json require and conflict blocks, and inspect the code for core APIs that October CMS 4 may have deprecated. Also confirm that your other required plugins and themes are compatible with October 4 before bundling this upgrade into a release.
- What are alternatives to this plugin for RSS ingestion?
- If October CMS is not in your stack, treat the evaluation as terminated and redirect to a library-level option. Good candidates are laminas/laminas-feed and willvincent/feeds, or a small ingestion service that stores parsed items and exposes them through your own API. Only use this plugin when October CMS fronts the application and you want a backend UI plus component out of the box.
- Is the plugin actively maintained, and what is the bus factor?
- It is a low-activity project with releases cut by a single contributor, which suggests limited maintenance bandwidth. Mitigate by pinning exact versions in composer.lock, avoiding floating constraints, and monitoring the repository for new releases and compatibility notes. Check whether a 3.3.x maintenance branch is published for teams staying on October CMS 3 and for how long it will be supported.
Weaver
How can I help you explore Laravel packages today?