Author Topic: RSS Feeds characters (version 4.2.8)  (Read 2946 times)

Offline Jeremy

  • Full Member
  • *****
  • Posts: 238
  • Karma: +1/-0
Re: RSS Feeds characters (version 4.2.8)
« Reply #15 on: January 24, 2017, 11:18:34 PM »
phpEnter Web Hosting
Remove also this code:

Code: [Select]
|replace:'&':' '
Social Bookmarking Script markerpaper.com

Offline Bix

  • Full Member
  • *****
  • Posts: 30
  • Karma: +0/-0
Re: RSS Feeds characters (version 4.2.8)
« Reply #16 on: January 24, 2017, 11:57:11 PM »
Yeah! That worked... Title now is perfect!!!!!!!!  :D

But the Text still remains unchanged....  :'(
« Last Edit: January 25, 2017, 12:32:47 AM by Bix »

Offline Jeremy

  • Full Member
  • *****
  • Posts: 238
  • Karma: +1/-0
Re: RSS Feeds characters (version 4.2.8)
« Reply #17 on: January 25, 2017, 03:26:26 PM »
Remove escape form decription:

Code: [Select]
|escape

Code: [Select]
<description>{if $newser[newser].images neq 0}<![CDATA[<img src="{$sitepath}/minthumb/{$newser[newser].images}" border="0" align="left" alt="" title="" />{$newser[newser].bamess|htmlspecialchars_decode|strip_tags|escape|truncate:280}]]>{else}{$newser[newser].bamess|htmlspecialchars_decode|strip_tags|escape|truncate:280}{/if}</description>
Social Bookmarking Script markerpaper.com

Offline Bix

  • Full Member
  • *****
  • Posts: 30
  • Karma: +0/-0
Re: RSS Feeds characters (version 4.2.8)
« Reply #18 on: January 25, 2017, 06:13:50 PM »
Done... Nothing! :(

But maybe I've an important hint: I don't know exactly why, but removing the code:

Code: [Select]
|escape|truncate:280
all starts to work perfectly.

I say "starts" because, obviously, removing that "truncate", the RSS Reader will retrieve ALL the content of the Story, removing tags, images, styles and also carriage returns. That means that the resulting LONG text will be very difficult to read.

Another solution that I've tried and works perfectly could be to get data from the Summary (db field: brief), where the text is already "truncated" and the decoding works like a charm (strangely, another thing that I don't understand, also using the same decoding used for field dbmess!!!)...

Maybe, with this new hint, you'll find a (real) solution. :)

« Last Edit: January 27, 2017, 05:56:43 AM by Bix »