Hi,

I'm just wondering if there is a reason why the rssBody1 links to the item in Plone rather than the /view template:

http://projects.quintagroup.com/products/browser/qRSS2Syndication/tags/0.5.1/skins/qrss2syndication/rssBody1.pt

This refers to:

<link tal:content="item/Identifier"></link>

Rather than to:

<link tal:content="string: item/Identifier + '/view'"></link>

Is there a reason why?

This causes a problem for us as we use this to create RSS1 news feeds in addition to our RSS2 vodcast feeds for videos.

Thus we have feeds that link directly to a video file instead of to the view page:

http://www.engagemedia.org/latestvideos/RSS

This will link to a video file directly, such as:
http://www.engagemedia.org/Members/SenatorBob/videos/sen_brown-01.avi

Many thanks,

Anna
EngageMedia.org

 

 

 

 

Hi Anna,

Identifier - is ExtensibleMetadata method which is equal to absolute_url(). In this case the line was borrowed from CMF/Plone template.

According to RSS specification <link> should lead to object, it is in fact. Object_URL+'/view' is not the one that proper for all Plone content, for example for document you would use just ObjectURL.

In this case my recommendation is to customize the rssBody1.pt as its fit your needs. I am not going to generalize the change into product at this point.

Volodymyr.

As a follow up.

In case of publishing Video files by feed you should look at RSS 2.0 feeds. The RSS 2.0 standard has extra tag for files/attachments inclusion - <enclosure>

Hi,

Thanks so much for your reply. Your point is taken re. customisation, and our issue here turned out to be to do with using ContentLicensing product. The ContentLicencing product was incorporated into the mix on our site, and overrides the templates of RSS1, using browser views style (zope3) . This applies only to content types that implement Products.ContentLicensing.DublinCoreExtensions.interfaces.ILicensable which is setup in ContentLicensing/DublinCoreExtensions/configure.zcml

 

As an aside, yes we are creating RSS2 feeds with enclosures for videos as you say, which is incorporated as part of the Plumi package we have produced for Plone:

http://plone.org/products/plumi/

 

Many thanks,

Anna