Thats possibly because its for the tt_content.text element - look at something for the tt_address.
See if tt_content makes use of parseFunc for the rendering of content on the front end. For instance the ccs_styled_content defines a lib.parseFunc_RTE that it uses in the BE for the rendering and display of the text contents of tt_content.text.20 Andrew Davis wrote: > something like this looked promising, but has no effect? can anyone be > more specific for me? > > > > tt_content.text.20.parseFunc.allowTags = p > > > thanks in advance, > Andrew > > > > > Tyler Kraft wrote: >> Just a quick guess but it probably has to do with the parseFunc for >> rendering that field on the FE. >> >> >> >> Andrew Davis wrote: >>> Having an odd issue with tt_address. I thought at first it had to do >>> with the rte i was using, but the rte seems to be working properly. >>> >>> 1. I am using tinyrte 1.6.6, tt_address 2.1.0 and typo3 4.1.2 >>> >>> 2. When i make an entry into tt_address description field, I can make >>> <p> breaks and save them. if i reload the record, the <p> are there. >>> >>> 3. When I load the record in the frontend, the <p> tags are converted >>> to line breaks, and the browser runs them all together (the breaks >>> are not rendered at all (this is normak behavior for browsers...) >>> >>> so my quesiton is how can i get tt_address to not convert <p> tags to >>> line breaks?! it is very weird. >>> >>> any help much appreciated, >>> thanks >>> >>> andrew _______________________________________________ TYPO3-english mailing list TYPO3-english@lists.netfielders.de http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english