Hi All,

I am not sure whether this is even a bug, or a configuration issue. I have been working with the WEC Devo Journal Extension on a couple of websites and I'm running into some issues. I thought at first that it might be because one of the sites I was trying to use it on was TYPO3 v.3.7.1, but just to make sure, I decided to try it on a test site we have running that is using the WEC Pre-release (TYPO3 v.3.8 ). I am using the most recent version of the extension downloaded both from this site, and the TYPO3 repository, and I have the most recent version of htmlArea running.

Here's the issue:

I am entering text into the Devo Content record in the backend. I am formatting the text, inserting line-breaks, etc. Everything looks great when I save it. I've even looked at the HTML content that the RTE generates by toggling the HTML source in htmlArea. All looks great.

But then, when I view it from the front-end, everything shifts up to one line. It looks like it's actually removing the <p> tags from the content and I am not sure how to fix this, or if it is a conflict of some kind. On the other hand, it seems to keep the <p> tag if a style is applied (such as italics or text color). It also seems to do ok with <h1> tag and <strong> tag.

This problem occurs on both sites, the v.3.1.7 and the v.3.8.

Has anyone else experienced this issue, and is there anything immediately that can be done to work around it?

Thanks for your help!

Barbara

Hi Barbara,

The problem is not with the Devo itself, but with the RTE handling TextArea content fields. What happens is that Typo3 does a transformation when your data is saved. And then when you go to edit it, it transforms it back. It does funny stuff with <p> tags...yet you can change its behavior.

There is documentation about it -- http://typo3.org/documentation/document-library/rtehtmlarea/Configuration-80/#oodoc_part_11286

Also, found a link to an article that may be helpful -- http://lists.netfielders.de/pipermail/typo3-english/2005-November/014574.html

With the TJ on the Ginghamsburg site, I setup special Page TSConfig that allowed this. Here it is below. You would paste this in either the root level of your site, or the top page where the storage folder is (or wherever you would edit the data for your Devotional).

RTE.default.proc {
dontConvBRtoParagraph = 1
preserveTags = UL, LI, TYPOCODE, MYTAG, P, Class, p
allowTagsInTypolists = p,br,font,b,i,u,a,img,span
overruleMode = 0
exitHTMLparser_db = 0
entrytHTMLparser_db = 0
exitHTMLparser_rte = 0
entryHTMLparser_rte = 0
remapParagraphTag = P
allowedClasses =
showButtons = removeformat

HTMLparser_db {
// TAGS ALLOWED
allowTags = h1, h2, h3, h4, h5, h6, div, p, br, ul, ol, li, pre, blockquote, strong, em, b, i, u, a, img, nobr, hr, center

// DO NOT REMOVE UNMATCHED TAGS
keepNonMatchedTags = 1
}
}

Note that some of this is different than the article and some of it may be the defaults (read the doco). This has extra stuff too...you may want to just try the dontConvBRtoParagraph and see if that fixes the problem.

-Dave

Hey Dave,

The typoscript did in fact work once I plugged it into the Devo page header. Thanks for pointing me in the right direction

Barbara

Hey Dave,

The typoscript did in fact work once I plugged it into the Devo page header. Thanks for pointing me in the right direction

Barbara