Opened 4 years ago

Last modified 12 months ago

#5032 new change

Generate feed XML for blog

Reported by: saroyanm Assignee:
Priority: Unknown Milestone:
Module: Websites Keywords:
Cc: greiner, juliandoucette, athornburgh, kvas, ferris, jsonesen Blocked By:
Blocking: Platform: Unknown / Cross platform
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):



We are not generating RSS and ATOM feeds for, which makes hard for user to keep up with changes

What to change

Generate RSS and ATOM feeds for and (Recent updates blog list).

Change History (11)

comment:1 Changed 4 years ago by saroyanm

  • Cc kvas added

I'm not yet sure about the module, I assume this should be in the alignment with the sitescript module, but at least we will be able to collect all the requirements here before applying the right module.

RSS specification link ->
ATOM specification link ->

comment:2 Changed 3 years ago by juliandoucette

  • Cc ferris added

If I remember correctly, adblockplus/cms does not add extensions to it's output. If that is true then we should be able to generate an RSS feed using get_pages_metadata, a template, and a page. I don't know if the server would recognize this file as an xml file and not an HTML file though.

Can you verify ferris and/or kvas?

Last edited 3 years ago by juliandoucette (previous) (diff)

comment:3 follow-up: Changed 3 years ago by ferris

  • Cc jsonesen added
  • Summary changed from Generate feed XML for blog to Generate feed XML for blog

Jon or Vasily should be able to answer regarding CMS.

Regarding file type, the server can be configured to set content type per path/filename. So if we have .rss files, we could configure their content-type to be application/rss+xml I think. Assuming that all content is just static files. Anyhow, I don't think browsers these days give RSS much special treatment. Perhaps we should offer an easy way for the reader to copy/paste the RSS URL.

comment:4 Changed 3 years ago by kvas

Hi Ferris and Julian. What you're proposing makes sense and I think it should work. If it doesn't and we can fix it with some help from CMS side, we'd be happy to look into this.

comment:5 Changed 3 years ago by juliandoucette

@kvas, @ferris I don't think that manually configuring file types in server config is a good solution.

Why not add extensions to CMS output and allow the extension to be defined as a page property?

comment:6 in reply to: ↑ 3 Changed 3 years ago by greiner

Replying to ferris:

Perhaps we should offer an easy way for the reader to copy/paste the RSS URL.

If it helps you can check out how I implemented it on my personal blog.

It's basically just a set of static links so pretty simple to implement.

comment:7 Changed 3 years ago by jsonesen

Hey all,

As a follow up to a discussion between Vasily, and I. We found that adding two extensions (the second being either html, md, or tmpl) will retain the extension you add prior to the final ext. (ie the filename would be: feed.rss.tmpl and the resulting file after generation is feed.rss) This at first glance seemed rather hacky and maybe not the cleanest solution. However, after some deliberation we came to the agreement that since the RSS feed would in fact be a template populated using a global as julian had mentioned earlier this actually is not so ugly.

What do you all think?

comment:8 Changed 3 years ago by juliandoucette

What do you all think?

Fine by me if our infrastructure servers it properly. Did you test that (HTTP headers)?

comment:9 Changed 3 years ago by kvas

According to Matze some minimal one time configuration will be necessary to make this work. I can follow up with him on this to make sure it's in place by the time any RSS files hit the website repositories.

comment:10 Changed 3 years ago by juliandoucette

  • Milestone cleanup deleted

comment:11 Changed 12 months ago by greiner

  • Component changed from Unknown to Websites
Note: See TracTickets for help on using tickets.