Featured text not working as 'expected'

chrisjlocke · #1 03-26-2008, 07:34 PM

Going on from this post:
http://www.monkeycms.com/forum/showt...=1707#post1707

I've added some featured text to some content, but the checkboxes along the side don't act the same way as for the main content text.

Heres some content (and the same featured text) with all three checkboxes ticked. Works fine.
http://www.sjamaldon.org.uk/content.php?contentid=233

With no checkboxes ticked, the content_text is fine, but the featured text doesn't display.
http://www.sjamaldon.org.uk/content.php?contentid=234

It only displays with the 'Parse BBCode' ticked. In fact, heres the same content with *just* 'Parse BBCode' ticked.
http://www.sjamaldon.org.uk/content.php?contentid=235

You'll also note in that last example, the content_text is not displaying the bold 'See?' text, but the featured text is. Obviously, its the featured_text at fault.

Colin · #2 03-26-2008, 08:12 PM

I'll take a look at this code - there were some parsing changes in the last release that may have broken things. I'll try and get a patch out tomorrow.

chrisjlocke · #3 10-17-2009, 10:55 PM

Bump. The 'add linebreaks' checkbox for the featured text doesn't appear to be working. (using v1.5.1)
Looking at the HTML source, its adding line breaks in the source, rather than line break tags, if you follow.

Colin · #4 10-18-2009, 06:45 AM

I'll look into this on Monday

Not sure off the top of my head what could be the problem - I'm sure I have it working on one site at least so I'll check.

Colin · #5 11-13-2009, 11:37 AM

Quote:

Originally Posted by chrisjlocke

Bump. The 'add linebreaks' checkbox for the featured text doesn't appear to be working. (using v1.5.1)
Looking at the HTML source, its adding line breaks in the source, rather than line break tags, if you follow.

I've been trying to replicate this - is it on indexes or content pages you have a problem? If it's the former then try using 'parsed_featured_text' in your templates, if it's the latter then I'm not seeing the prob in 1.5.2 so will have to get you to retest with that version when its out.