Due to recent updates, all users are required to create an Altair One account to login to the RapidMiner community. Click the Register button to create your account using the same email that you have previously used to login to the RapidMiner community. This will ensure that any previously created content will be synced to your Altair One account. Once you login, you will be asked to provide a username that identifies you to other Community users. Email us at Community with questions.
Increased tolerance in "Read RSS Feed"
Contributor I
[I think this lives here rather than problems/support but please advise if not]
"Read RSS Feed" is great but Wordpress is in the habit of providing a shortened text for <description> (we're in RSS 2) and the full post text in <content:encoded> (see snippet below).
"Read RSS Feed" captures only "description" contents.
It would be great for "Read RSS Feed" to cope with this rather irritating practice from WP, either through some programmed heuristics or a user-controlled parameter in the "Read RSS Feed" operation.
Cheers, Adam
--------
The Wordpress "irritating practice":
<description><![CDATA[(10th in my logic of competence series)
In this series of posts I’ve used many terms as a part of my attempts to communicate on these topics. Now I offer definitions for or notes about both the concepts I’ve used in the blog posts so far, and related ones drawn from a range of other work, [...]]]></description>
<content:encoded><![CDATA[<p>(10th in my { lots of content removed from here } </content:encoded>
"Read RSS Feed" is great but Wordpress is in the habit of providing a shortened text for <description> (we're in RSS 2) and the full post text in <content:encoded> (see snippet below).
"Read RSS Feed" captures only "description" contents.
It would be great for "Read RSS Feed" to cope with this rather irritating practice from WP, either through some programmed heuristics or a user-controlled parameter in the "Read RSS Feed" operation.
Cheers, Adam
--------
The Wordpress "irritating practice":
<description><![CDATA[(10th in my logic of competence series)
In this series of posts I’ve used many terms as a part of my attempts to communicate on these topics. Now I offer definitions for or notes about both the concepts I’ve used in the blog posts so far, and related ones drawn from a range of other work, [...]]]></description>
<content:encoded><