“To enable an RSS Feed for your collection, open the RSS and Sitemap settings and switch on the RSS toggle. This activates a dynamic feed for the collection, allowing users and apps to subscribe to updates without any extra setup on your server. It’s worth noting that the CMS doesn’t generate a physical file. The feed is built dynamically whenever it’s requested, so you won’t see any RSS files on your server.”
Just a quick update: I’ve added support for generating physical XML files for both RSS feeds and sitemaps.
You can now link directly to these files, and they’re generated automatically for you.
The URLs are exposed on the collection object and can be output using {{ collection.rssURL }} and {{ collection.sitemapURL }}.
If you need to force a rebuild of the xml files, you can append ?regenerate_rss=1 and/or ?regenerate_sitemap=1 to the URL of the page where the Collection is used.
No (I think) - that’s the website’s overall sitemap.
We’re talking about the sitemap for the blog … ie: sitemap-blog.xml
That’s my understanding anyway :
Jol
@ben I have noticed that there is a long lag between the files showing up on the server when you change their names. I guess I should have used the method of forcing an update. Which I eventually did, and that caused them to be updated.
The other thing I have noticed is that if I add a new post to the blog, the only way I can get it to show up is if I force an update. I would have thought there would be a more immediate update.
Is there a way of setting new posts to update immediately?
Looking at the blog sitemap, I see some code that deals with the change frequency, which seems to be set to “weekly”. Can this be changed?
It might be nice to have some toggles in the properties to force the updates.