nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

RSS feed (incoming)

prof_brazen_guff

Hi all

I'm developing a component to embed external rss feeds in our website using LS 3.0.2. I've seen a thread elsewhere in this forum which refers to a component which is bundled with this LS version called RSS Feed Viewer. I can't find this component, so is it possible it wasn't installed for me? If so, anyone know how I can get hold of it?

Thanks in advance for your help

Paul

Find more posts tagged with

Comments

msrinivas

It is installed as part of the post installation tasks (after reboot). You will find the component at:

//server-name/default/main/component-guide/WORKAREA/shared/sites/Component Guide/Social Computing

HTH

new_report_1.rptdesign

prof_brazen_guff

Thanks for the prompt response.

We definitely don't have this folder. How can I get hold of its contents?

Thanks again

Paul

msrinivas

Did you get the post-installation screens after re-boot of the server when you installed/upgraded?

Does your license key for TS 6.7.2 include SitePub?

Do you have any errors in the install/upgrade log?

In the post-installation script it is suggested not to run it manually. If the above are fine then I would suggest you open a support case with IWOV.

prof_brazen_guff

Thanks again for the advice. No errors that I can see, so I've raised with IW support.

Paul

Stokes

We definitely don't have this folder. How can I get hold of its contents?

Paul,

I don't have 3.0.2, but in 3.1 it just uses a built-in external method Web.urlGet(). If you have the same Java class in your install, then your component can have a Content XML like this:

Content XML


<Data>
    <Datum ID="MAXITEMS" Name="Maximum Number of Items" Type="Number">3</Datum>
    <Datum ID="SHOWPUBDATE" Name="Include Publish Date" Type="Boolean">true</Datum>
    <External>
        <Parameters>
            <Datum ID="feedURL" Name="URL" Type="String">http://rss.news.yahoo.com/rss/topstories</Datum>
        </Parameters>
        <Object Scope="local">com.interwoven.livesite.external.runtime.Web</Object>
        <Method>urlGet</Method>
    </External>
</Data>

That might need to be adapted if the package name is slightly different or something, but I'd bet you have that class too.

That gives you the raw XML from the RSS feed as part of the XML available to the component stylesheet, so you can transform it how you like. If you want to see what the 3.1 component does--not even sure what it looks like and it might need adapting as well, but I don't suppose it will hurt to post it--here are the other two parts.

Appearance XML


<Properties ComponentID="1186521799982">
    <Datum ID="BODYCLASS" Name="Component CSS Class" Type="String">rss-body</Datum>
    <Datum ID="ITEMCLASS" Name="Item CSS Class" Type="String">rss-item</Datum>
    <Datum ID="TITLECLASS" Name="Title CSS Class" Type="String">rss-title</Datum>
    <Datum ID="DATECLASS" Name="Date and Time CSS Class" Type="String">rss-date</Datum>
    <Datum ID="STORYCLASS" Name="Story CSS Class" Type="String">rss-story</Datum>
</Properties>

Appearance XSL


<!DOCTYPE html-entities SYSTEM "http://www.interwoven.com/livesite/xsl/xsl-html.dtd">
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
  <!-- Skin: Default (Default Browser Type) -->

  <xsl:include href="http://www.interwoven.com/livesite/xsl/HTMLTemplates.xsl"/>
  <xsl:include href="http://www.interwoven.com/livesite/xsl/StringTemplates.xsl"/>


  <xsl:template match="/">
    <xsl:choose>
      <xsl:when test="0 = string-length(/Properties/Datum[@ID='BODYCLASS'])">
        <div>
          <xsl:attribute name="style">font-size:75%;font-family:sans-serif</xsl:attribute>
          <xsl:apply-templates select="/Properties/Data/Result/Response/rss/channel" />
        </div>
      </xsl:when>
      <xsltherwise>
        <div>
          <xsl:attribute name="class"><xsl:value-of select="/Properties/Datum[@ID='BODYCLASS']" /></xsl:attribute>
          <xsl:apply-templates select="/Properties/Data/Result/Response/rss/channel" />
        </div>
      </xsltherwise>
    </xsl:choose>
  </xsl:template>

  <xsl:template match="channel">
    <xsl:for-each select="item">
      <xsl:sort select="pubDate" order="descending"/>
      <xsl:if test="position() &lt;= /Properties/Data/Datum[@ID='MAXITEMS']">
        <xsl:call-template name="stories">
          <xsl:with-param name="title" select="title"/>
          <xsl:with-param name="link" select="link"/>
          <xsl:with-param name="pubDate" select="pubDate"/>
          <xsl:with-param name="description" select="description"/>
        </xsl:call-template>
      </xsl:if>
    </xsl:for-each>
  </xsl:template>


  <xsl:template name="stories">
    <div>
      <xsl:attribute name="class"><xsl:value-of select="/Properties/Datum[@ID='ITEMCLASS']" /></xsl:attribute>

      <xsl:choose>
        <xsl:when test="0 = string-length(/Properties/Datum[@ID='TITLECLASS'])">
          <div style="padding:10px 2px 0px 2px; font-size:125%; font-weight:bold;">
            <a>
              <xsl:attribute name="href"><xsl:value-of select="link"/></xsl:attribute>
              <xsl:value-of select="title"/>
            </a>
          </div>
        </xsl:when>
        <xsltherwise>
          <div>
            <xsl:attribute name="class"><xsl:value-of select="/Properties/Datum[@ID='TITLECLASS']" /></xsl:attribute>
            <a>
              <xsl:attribute name="href"><xsl:value-of select="link"/></xsl:attribute>
              <xsl:value-of select="title"/>
            </a>
          </div>
        </xsltherwise>
      </xsl:choose>

      <xsl:if test="/Properties/Data/Datum[@ID='SHOWPUBDATE'] = 'true'">
        <div>
        <xsl:attribute name="class"><xsl:value-of select="/Properties/Datum[@ID='DATECLASS']" /></xsl:attribute>
          <xsl:value-of select="pubDate"/>
        </div>
      </xsl:if>
      <div>
      <xsl:attribute name="class"><xsl:value-of select="/Properties/Datum[@ID='STORYCLASS']" /></xsl:attribute>
        <xsl:value-of select="description" disable-output-escaping="yes"/>
      </div>
    </div>
  </xsl:template>


</xsl:stylesheet>

Enjoy,
Stokes

prof_brazen_guff

Hi again Stokes

That's great! Thanks v much. We do have the java class, so I'll give this a go.

Paul

prof_brazen_guff

Me again ...

I've built a working component based on the code you've given me, but (there's always a but ... ) it doesn't seem to work for all feeds. For example, it will happily display the BBC news feed (http://newsrss.bbc.co.uk/rss/newsonline_uk_edition/front_page/rss.xml), but when I try to display this one http://www.pebbleweb.co.uk/hull/rss.aspx/blog/573, I just see the raw feed xml in the xml viewer when previewing the component. Any ideas as to why this is happening wopuld be much appreciated. I confess to not knowing too much about this area ...

Thanks again

Paul

Stokes

I've built a working component based on the code you've given me, but (there's always a but ... ) it doesn't seem to work for all feeds. For example, it will happily display the BBC news feed (http://newsrss.bbc.co.uk/rss/newsonline_uk_edition/front_page/rss.xml), but when I try to display this one http://www.pebbleweb.co.uk/hull/rss.aspx/blog/573, I just see the raw feed xml in the xml viewer when previewing the component. Any ideas as to why this is happening wopuld be much appreciated. I confess to not knowing too much about this area ...

Paul,

I thought I posted a reply to this thread but it's not showing up. (Am I being censored? :-) Anyway, now that you mentioned it, I recall a problem with the built-in class... it's looking for an HTTP content type of "text/xml", and when it finds anything else at all, it just returns the content in a CDATA section instead of parsing into XML elements. So I'd bet that some of the services you tried return text/xml and others return application/xml or something else. A silly technicality, but I think that's your problem.

What I did in the past was write my own external. I started to ask permission to post that code here, but after looking at it it has other hooks and such that make it more complicated than you need. So I'll post the basics of it here and if it's helpful I can elaborate.


String urlString = ...;
URL url = new URL(urlString);
URLConnection connection = url.openConnection();
InputStream is = new BufferedInputStream(connection.getInputStream());
Document doc = Dom4jUtils.newDocument();
// parse the XML stream into a DOM
Document xml = Dom4jUtils.newDocument(is);
// wrap this XML tree in a top-level element called "Xml"
doc.addElement("Xml").add(xml.getRootElement().detach());
return doc;

That relies on the Dom4jUtils class, which is in livesite.jar or one of those. Other than that, it should be straightforward... just parses the contents into XML regardless of content type. Of course, you'd have to add your own exception handling, but you get the idea. This would return a Dom4j Document, so it could be part of a method called as an External from a component.

Stokes.

prof_brazen_guff

Paul,

I thought I posted a reply to this thread but it's not showing up. (Am I being censored? :-) Anyway, now that you mentioned it, I recall a problem with the built-in class... it's looking for an HTTP content type of "text/xml", and when it finds anything else at all, it just returns the content in a CDATA section instead of parsing into XML elements. So I'd bet that some of the services you tried return text/xml and others return application/xml or something else. A silly technicality, but I think that's your problem.

What I did in the past was write my own external. I started to ask permission to post that code here, but after looking at it it has other hooks and such that make it more complicated than you need. So I'll post the basics of it here and if it's helpful I can elaborate.
String urlString = ...;
URL url = new URL(urlString);
URLConnection connection = url.openConnection();
InputStream is = new BufferedInputStream(connection.getInputStream());
Document doc = Dom4jUtils.newDocument();
// parse the XML stream into a DOM
Document xml = Dom4jUtils.newDocument(is);
// wrap this XML tree in a top-level element called "Xml"
doc.addElement("Xml").add(xml.getRootElement().detach());
return doc;
That relies on the Dom4jUtils class, which is in livesite.jar or one of those. Other than that, it should be straightforward... just parses the contents into XML regardless of content type. Of course, you'd have to add your own exception handling, but you get the idea. This would return a Dom4j Document, so it could be part of a method called as an External from a component.

Stokes.

Thanks (yet again) Stokes. This sounds just like the problem I'm experiencing, so I'll have a go at writing my own external to solve the issue.

Paul