I’ve upgraded my RSS Feed Integration library for Optimizely CMS to support Optimizely CMS 13.
Version 3.0.0 is currently released as a beta to allow early testing with the CMS 13 preview. This version will become stable once CMS 13 reaches its final release.
If you're planning your CMS 12 → 13 migration, this release allows you to validate RSS behavior ahead of time.
Breaking Changes in 3.0.0
There are two important changes to be aware of.
Scheduled Job Must Be Re-Executed
After upgrading, you must re-launch the scheduled job once in order to regenerate the RSS feed.
Why?
The compiled XML feed files will now be stored in a different location (see below). The plugin will not automatically detect the old files.
A single execution of the scheduled job resolves the issue.
SiteDefinition → Application (CMS 13 Architecture Change)
Under Optimizely CMS, the transition from SiteDefinition to Application removes the Id property.
In previous versions:
-
The
SiteDefinition.Idwas used to determine where compiled RSS XML files were stored.
In CMS 13:
Applicationno longer exposes anId.- The save path must now rely on the normalized application name instead.
Impact
Because of this change:
- The storage path of compiled RSS XML files changes.
- Existing RSS files generated under CMS 12 will not be found.
- The scheduled job must be executed once to regenerate them in the new location.
Migration Summary
If you are upgrading:
- Update to version 3.0.0-beta
- Deploy your CMS 13 preview environment
- Run the RSS scheduled job once
- Validate your feed output
That’s it. If you are preparing your CMS 13 migration roadmap, this beta gives you a safe way to validate RSS generation ahead of the official release.