Sponsors, are you providing an wordpress rss feed for affs? [content:encoded] FIX!!!

[Jace]

there are a few pieces of software out there that aren't outputting anything past [content:encoded] tags from a wordpress rss2.0 feed

I found a fix for everyone

http://pixane.net/index.php/Wordpress_RSS

keep in mind, that if you are providing a rss feed for affiliates that is being created by wordpress, then anyone using rss2blog and a few other pieces of software CAN NOT use your feed, this will fix it

I have not personally tried this, but judging from the data I can see, it shoudl work

[martinsc]

thanks. i was looking for that

[teksonline]

Without looking is this the fix?

$encodedcontent = preg_replace('/\'/s', 'hahaha8217;', $content);



Problem with the encoded feed's as I look at most feeds they are not encoding it properly...

[Jace]

Originally Posted by teksonline

Without looking is this the fix?

$encodedcontent = preg_replace('/\'/s', 'hahaha8217;', $content);



Problem with the encoded feed's as I look at most feeds they are not encoding it properly...

here it is

--- /root/wp-rss2.php   2006-01-17 13:19:15.000000000 -0500
+++ /var/web/wordpress/wp-rss2.php      2006-01-17 13:20:52.000000000 -0500
 -38,9 +38,9 @@

                <guid isPermaLink="false"><?php the_guid(); ?></guid>
 <?php if (get_settings('rss_use_excerpt')) : ?>
-               <description><![CDATA[<?php the_excerpt_rss() ?>]]></description>
+               <description><![CDATA[<?php the_content('', 0, '') ?>]]></description>
 <?php else : ?>
-               <description><![CDATA[<?php the_excerpt_rss() ?>]]></description>
+               <description><![CDATA[<?php the_content('', 0, '') ?>]]></description>
        <?php if ( strlen( $post->post_content ) > 0 ) : ?>
                <content:encoded><![CDATA[<?php the_content('', 0, '') ?>]]></content:encoded>
        <?php else : ?>

[Jace]

bump for all sponsors using wordpress for their rss feeds

[CamsLord]

bump good thread

[Jace]

Originally Posted by CamsLord

bump good thread

I just wish more sponsors would take this seriously

there are a few of us with a good amount of traffic that aren't using rss feeds because they have that content:encoded tag in them

from what viki at realsexcash is saying, it is a code that is ahead of it's time and not all rss tools will push what is inside those tags through to the sites.

regardless, it is something that needs to be fixed on all rss feeds for now, at last until new versions of rss software comes out and they support it

[bangman]

Thanks Jace, I have been looking for a solution for 2 days.

[viki]

I have another easy solution in the form of a WP plugin. If anyone wants it, ICQ 228 263 454.

[Jace]

Originally Posted by viki

I have another easy solution in the form of a WP plugin. If anyone wants it, ICQ 228 263 454.

wow viki, you rock....can you email it to me?

[viki]

Originally Posted by Jace

wow viki, you rock....can you email it to me?

Sent. Now where's my traffic, bitch?

[Jace]

Originally Posted by viki

Sent. Now where's my traffic, bitch?

hahaha..coming shortly, adding the feeds back in now

[Jace]

Originally Posted by viki

Sent. Now where's my traffic, bitch?

I just pushed through a single post from your feeds to every single one of my blogs...so, you now have the top post on 13 blogs of mine for the next 24 hours

[teksonline]

Just want to add, under every occurence of people asking to remove content:encoded tags, the problem has been found to be improperly encoded html breaking the feeds

I want everyone to please consider dropping rss2blog. If they are a company that does not want to conform to rss 2.0 specifications then this is a problem company, Specifications are setup for a reason. RSS is a serious problem "protocol" for sake of a better term.

As it is unclear as to who the originators are, and whatnot, everyone is trying to control it, and breaking defined protocol specs to do so because of their own beliefs.

These companies are only going to bring more problems to the table for the future of RSS, if they are not going to support the specified specs, then its like breaking the rules of anything in existence based on a sole persons interpretation.(ANARCHY) (i.e. I killed him and it was ok because he looked at me funny)...

Whether or not the future will hold for <content:encoded> is a plausable concern, but should be addressed via versioning, but so far nothing indicates it's a problem or bad solution, only a few badly coded rss feeds (I had the same problem learning to code rss feeders just recently)

[fris]

awesome, this is a good tool