Jump to content

RSS import request ( to remove what looks like limitation)


msg

Recommended Posts

Posted

After i log a call for support for RSS import, it was propose to post request here.

When we want to import RSS looks like the suite request a channel

«...It looks like it is because they do not include any channel information within that Feedburner....»

The same RSS feed use in other RSS reader work fine

So the request is to make sure we can import any RSS feed. Example to validate, if Outlook/google reader can open it Invision suite should be able too. In my case this is important as I have multiple members having external blog or partner with RSS feed.

In a near future I look to establish partnership with partner where RSS will be one way to exchange information between communities.

Not sure if this can be done over an update or if it need to wait for a major update like IPS V4.0 any feedback from development will be appreciate.

Posted

Thank you Brandon for the link.

Any chance this can be in the next specs for 4.0? or update for 3.4?

It might be a minor limitation, but it seems like it prevent members to link their Blog to the community.

I found a place where it proposes to use this for RSS format.

http://david-merritt.blogspot.ca/feeds/posts/default?alt=rss

But it is not successfully recognized by IPBoard

IP.Board Message

Validation errors for http://david-merritt.blogspot.ca/feeds/posts/default?alt=rss
·HTTP Status Code: 302 (Moved Temporarily)
·XML error: not well-formed (invalid token) at line 1

Posted

Thank you Brandon for the link.

Any chance this can be in the next specs for 4.0? or update for 3.4?

It might be a minor limitation, but it seems like it prevent members to link their Blog to the community.

I found a place where it proposes to use this for RSS format.

http://david-merritt.blogspot.ca/feeds/posts/default?alt=rss

But it is not successfully recognized by IPBoard

IP.Board Message

Validation errors for http://david-merritt.blogspot.ca/feeds/posts/default?alt=rss
·HTTP Status Code: 302 (Moved Temporarily)
·XML error: not well-formed (invalid token) at line 1

Simply providing information.

That suggested url for RSS format just does an immediate 302 redirect to the ATOM format, thus the code is yet again trying to parse ATOM expecting RSS.

Will overcome this limitation at this time(globally).
I have nothing at all against ATOM support going core, is just one less hook to me for that application's functionality. :smile:
  • 8 months later...
  • 1 year later...

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...