one time I have seen a fully formated feed output, but after that the format is ignored and instead you will see html tags interpreted as pure text. See example url.
1) HTML isn't legal in feeds according the RSS specification. Can you tell me what the URL of the feed is so I can see what it's using to encode the HTML?
2) Allowing arbitrary HTML like that to run on your website presents security risks.
WSN Codes are switched on. Today the wsn codes are resolved and I see images and links in the feed data.
With Beta 14 I had the same situation (see updates above). Some times I saw the html tags written on detail page and sometimes I saw the images, links and the other html things.
Comments on Feed HTML format ignored
Forum Regular
Usergroup: Customer
Joined: Dec 20, 2007
Location: Germany
Total Topics: 33
Total Comments: 106
Hi Paul,
one time I have seen a fully formated feed output, but after that the format is ignored and instead you will see html tags interpreted as pure text. See example url.
Thanx,
Frank
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
1) HTML isn't legal in feeds according the RSS specification. Can you tell me what the URL of the feed is so I can see what it's using to encode the HTML?
2) Allowing arbitrary HTML like that to run on your website presents security risks.
Forum Regular
Usergroup: Customer
Joined: Dec 20, 2007
Location: Germany
Total Topics: 33
Total Comments: 106
In this case the feed url is
http://feeds2.feedburner.com/klaus_b
Today I saw on my site the fully formatted feed again.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
For security reasons it's a bad idea to show the HTML as it is, but beta 15 should translate as much as it can to WSN codes.
Forum Regular
Usergroup: Customer
Joined: Dec 20, 2007
Location: Germany
Total Topics: 33
Total Comments: 106
After updating to Beta 15 there are following errors while selecting details on entry with feed defintion:
Fatal error: Call to undefined function translatefeedcontent() in .../classes/onelink.php on line 2368
I have added in link.php
require_once 'includes/addeditfuncs.php';
at the top, so my site doesn't get errors and g**glebot will be happy
After doing that I see wsncodes in feed output on detailspage... Is this correct?
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Yes, I'll move the function to a file available in link.php. I must've only checked on the non-link feed system.
I'll fixed the {FEED var processing to parse the WSN codes.
Forum Regular
Usergroup: Customer
Joined: Dec 20, 2007
Location: Germany
Total Topics: 33
Total Comments: 106
With your fix the wsncodes are visible in the feed data. Please have a look at www.blog-finden.de/entwickl...und-c-spass-macht--34.html
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Do you have WSN Codes switched off? That's the only scenario where it's set to leave it like that.
Forum Regular
Usergroup: Customer
Joined: Dec 20, 2007
Location: Germany
Total Topics: 33
Total Comments: 106
WSN Codes are switched on. Today the wsn codes are resolved and I see images and links in the feed data.
With Beta 14 I had the same situation (see updates above). Some times I saw the html tags written on detail page and sometimes I saw the images, links and the other html things.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Are these different feeds, or the exact same feed on the exact same details page on a different day with nothing being changed?
Can you see any pattern of what could be different in the different scenarios?
Forum Regular
Usergroup: Customer
Joined: Dec 20, 2007
Location: Germany
Total Topics: 33
Total Comments: 106
It is every time the same feed on the same details page... and the feed hasn't changed since this bug report. Please see example url above.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Are you talking about some spots not parsing while others do on the same page? See this screenshot:
Attached Files:
Forum Regular
Usergroup: Customer
Joined: Dec 20, 2007
Location: Germany
Total Topics: 33
Total Comments: 106
Hi Paul,
begining with RC1 I haven't seen the problem any more. Now its look like in your screenshot.
Before RC1 (Beta) you could see all wsncodes in the output, like the one ypu have marked in ypur screenshot.
Best Regards,
Frank
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Odd, I don't recall making a new change intended to be related to this in RC 1. Hopefully it stays consistent...