<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>TYPO3-Addict &#187; RTE</title>
	<atom:link href="http://www.typo3-addict.com/category/rte/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.typo3-addict.com</link>
	<description>For those addicted to TYPO3</description>
	<lastBuildDate>Wed, 06 Jul 2011 08:08:32 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>TYPO3: RTE embed / iframe tag</title>
		<link>http://www.typo3-addict.com/2011/04/typo3-rte-embed-iframe-tag-tt_news/</link>
		<comments>http://www.typo3-addict.com/2011/04/typo3-rte-embed-iframe-tag-tt_news/#comments</comments>
		<pubDate>Thu, 28 Apr 2011 13:52:43 +0000</pubDate>
		<dc:creator>Maarten</dc:creator>
				<category><![CDATA[RTE]]></category>
		<category><![CDATA[Snippets]]></category>
		<category><![CDATA[TSConfig]]></category>
		<category><![CDATA[Configuration]]></category>
		<category><![CDATA[Typoscript]]></category>

		<guid isPermaLink="false">http://www.typo3-addict.com/?p=1052</guid>
		<description><![CDATA[According to Google Analytics a lot of people are currently looking for a way to use embed tags within the (tt_news) RTE. By default the TYPO3 RTE will remove these embed tags, but it&#8217;s fairly easy to change this. In this tutorial I&#8217;ll show you how to insert an iframe, within the TYPO3 RTE. Embedding [...]]]></description>
			<content:encoded><![CDATA[<p>According to Google Analytics a lot of people are currently looking for a way to use embed tags within the (tt_news) RTE. By default the TYPO3 RTE will remove these embed tags, but it&#8217;s fairly easy to change this. In this tutorial I&#8217;ll show you how to insert an iframe, within the TYPO3 RTE.</p>
<p><span id="more-1052"></span><br />
<strong>Embedding a Vimeo video </strong></p>
<p>Vimeo uses an iframe:<br />
<iframe src="http://player.vimeo.com/video/16458561?title=0&amp;byline=0&amp;portrait=0" frameborder="0" height="225" width="400"></iframe></p>
<pre>&lt;iframe src="http://player.vimeo.com/video/16458561?title=0&amp;amp;byline=0&amp;amp;portrait=0" frameborder="0" height="225" width="400"&gt;&lt;/iframe&gt;</pre>
<p>The most obvious way would be: Switch to HTML modus in the RTE, paste the code and save the content element. But as you might have experienced, this way you&#8217;ll end up with a nice HTML embed code printed in the frontend. Not so useful&#8230;</p>
<p><strong>How to fix this?!</strong><br />
Since Vimeo uses an iframe, we need to make sure the RTE accepts this iframe-tag. So we need to change RTE behaviour when saving the content element or tt_news record. Insert the following TSConfig configuration into the Page TSConfig field:</p>
<pre>RTE.default.proc.allowTags := addToList(iframe)
RTE.default.proc.entryHTMLparser_db.allowTags := addToList(iframe)</pre>
<p>If you want to insert the iframe outside of a block tag like a P or a DIV, than you&#8217;ll need to following as well:</p>
<pre>
RTE.default.proc.allowTagsOutside := addToList(iframe)
</pre>
<p>Now the RTE will preserve the iframe when saving. But&#8230; still no iframe in the frontend! <img src='http://www.typo3-addict.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /><br />
The extension css_styled_content doesn&#8217;t render an iframe by default, so let&#8217;s change this:</p>
<p>In your TypoScript constants add the iframe to the following (default) code:</p>
<pre>styles.content.links {
  allowTags  (
         b,i,u,a,img,br,div,center,pre,font,hr,sub,sup,p,strong,
         em,li,ul,ol,blockquote,strike,del,ins,span,h1,h2,h3,h4,
         h5,h6,address,iframe
  )
}</pre>
<p>Take a look in the frontend <img src='http://www.typo3-addict.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  If everything went well you can now see the Vimeo videoplayer.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.typo3-addict.com/2011/04/typo3-rte-embed-iframe-tag-tt_news/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
		<item>
		<title>TYPO3: Replace RTE content through TypoScript</title>
		<link>http://www.typo3-addict.com/2011/04/typo3-replace-rte-content-through-typoscript/</link>
		<comments>http://www.typo3-addict.com/2011/04/typo3-replace-rte-content-through-typoscript/#comments</comments>
		<pubDate>Fri, 08 Apr 2011 18:49:24 +0000</pubDate>
		<dc:creator>Maarten</dc:creator>
				<category><![CDATA[RTE]]></category>
		<category><![CDATA[Snippets]]></category>
		<category><![CDATA[TYPO3]]></category>
		<category><![CDATA[Typoscript]]></category>

		<guid isPermaLink="false">http://www.typo3-addict.com/?p=1013</guid>
		<description><![CDATA[Ever wanted to replace a single word throughout a whole TYPO3 website? Of even better: You know it will have to be changed in time? Like a year or a name? The solution is quite simple yet not seen as often as you might think. Most people know they can set a TypoScript constant to [...]]]></description>
			<content:encoded><![CDATA[<p>Ever wanted to replace a single word throughout a whole TYPO3 website? Of even better: You know it will have to be changed in time? Like a year or a name? The solution is quite simple yet not seen as often as you might think. Most people know they can set a TypoScript constant to easily change a TypoScript setup value along the way, but your actual content is most of the time written in the RTE. With this little TypoScript snippet you can replace RTE content with something else.</p>
<p><span id="more-1013"></span></p>
<p>Example 1: We want our customers to contact us by phone, but the phone number changes all the time.</p>
<p>RTE content:</p>
<pre>Please call us: phonenumber</pre>
<p>In TypoScript:</p>
<pre>page {
  stdWrap.parseFunc.short {
    phonenumber =  + 1 555-3141
  }
}</pre>
<p>In the frontend &#8216;phonenumber&#8217; will now be replaced with the actual number. Quite easy. Combined with <a title="TYPO3: How to use TypoScript Conditions" href="http://www.typo3-addict.com/2009/11/typo3-how-to-use-typoscript-conditions/">TypoScript conditions</a>, this is a really powerful way of content rendering.</p>
<p>Example 2: We want customers to call a different phone number during business hours.</p>
<p>RTE content:</p>
<pre>Please call us: phonenumber</pre>
<p>In TypoScript:</p>
<pre>[hour =&lt; 9] &amp;&amp; [hour =&gt;18]
page {
  stdWrap.parseFunc.short {
    phonenumber =  + 1 555-3141
  }
}
[else]
page {
  stdWrap.parseFunc.short {
    phonenumber =  + 1 555-5131
  }
}
[end]</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.typo3-addict.com/2011/04/typo3-replace-rte-content-through-typoscript/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>TYPO3: Click and Enlarge in RTE tt_news</title>
		<link>http://www.typo3-addict.com/2010/06/typo3-click-and-enlarge-in-rte-tt_news/</link>
		<comments>http://www.typo3-addict.com/2010/06/typo3-click-and-enlarge-in-rte-tt_news/#comments</comments>
		<pubDate>Wed, 02 Jun 2010 12:55:32 +0000</pubDate>
		<dc:creator>Maarten</dc:creator>
				<category><![CDATA[Extensions]]></category>
		<category><![CDATA[RTE]]></category>
		<category><![CDATA[Snippets]]></category>
		<category><![CDATA[tt_news]]></category>
		<category><![CDATA[Typoscript]]></category>

		<guid isPermaLink="false">http://www.typo3-addict.com/?p=990</guid>
		<description><![CDATA[I needed an image in the RTE to support the &#8216;click and enlarge&#8217; option in tt_news. Now, I used Google to find a solution but no luck, although it seems I&#8217;m not the only one trying to make this work. Looks like this isn&#8217;t as easy as it would sound.. Read more for the solution! [...]]]></description>
			<content:encoded><![CDATA[<p>I needed an image in the RTE to support the &#8216;click and enlarge&#8217; option in tt_news. Now, I used Google to find a solution but no luck, although it seems I&#8217;m not the only one trying to make this work. Looks like this isn&#8217;t as easy as it would sound..</p>
<p>Read more for the solution!</p>
<p><span id="more-990"></span></p>
<p><strong>How to set the click and enlarge option for the RTE in tt_news:</strong></p>
<p>Step 1:<br />
Include the static template: Clickenlarge Rendering (rtehtmlarea)</p>
<p>Now the click and enlarge rendering should work for normal content elements, but still no result for tt_news.</p>
<p>Step 2:<br />
Add the following TypoScript to your setup:</p>
<pre>
# Rendering RTE tt_news. Use the normal RTE parseFunc
# configuration for tt_news rte content
plugin.tt_news {
        general_stdWrap {
   	      parseFunc < tt_content.text.20.parseFunc
        }
}
</pre>
<p>Your Done <img src='http://www.typo3-addict.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>It turns out tt_news uses another way of rendering the RTE, so this should be reversed.</p>
<p>Update: It seems this snippet is actually part of the tt_news static template but out-commented... makes me wonder why?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.typo3-addict.com/2010/06/typo3-click-and-enlarge-in-rte-tt_news/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TYPO3: Create new folders and upload files through the RTE</title>
		<link>http://www.typo3-addict.com/2008/12/create-new-folders-and-upload-files-through-the-rte/</link>
		<comments>http://www.typo3-addict.com/2008/12/create-new-folders-and-upload-files-through-the-rte/#comments</comments>
		<pubDate>Wed, 10 Dec 2008 09:49:26 +0000</pubDate>
		<dc:creator>Maarten</dc:creator>
				<category><![CDATA[RTE]]></category>
		<category><![CDATA[TSConfig]]></category>

		<guid isPermaLink="false">http://blog.emaux.nl/?p=179</guid>
		<description><![CDATA[Default settings of the HTMLArea RTE do not allow you to create new folders or upload files to the fileadmin. 2 simple TSConfig lines can enable this. For your convenience: ## Enable upload field options.uploadFieldsInTopOfEB = 1  ## Enable folder create options.createFoldersInEB = 1  Check out the screenshot:]]></description>
			<content:encoded><![CDATA[<p>Default settings of the HTMLArea RTE do not allow you to create new folders or upload files to the fileadmin. 2 simple TSConfig lines can enable this.</p>
<p>For your convenience:</p>
<pre>
## Enable upload field
options.uploadFieldsInTopOfEB = 1  

## Enable folder create
options.createFoldersInEB = 1 
</pre>
<p>Check out the screenshot:</p>
<p><span id="more-179"></span></p>
<p><a href="http://blog.emaux.nl/wp-content/uploads/2008/12/upload_create_rte.png"><img class="alignnone size-medium wp-image-181" title="upload_create_rte" src="http://blog.emaux.nl/wp-content/uploads/2008/12/upload_create_rte-300x197.png" alt="" width="300" height="197" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.typo3-addict.com/2008/12/create-new-folders-and-upload-files-through-the-rte/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TYPO3: A default RTE configuration</title>
		<link>http://www.typo3-addict.com/2008/08/my-default-rte-configuration/</link>
		<comments>http://www.typo3-addict.com/2008/08/my-default-rte-configuration/#comments</comments>
		<pubDate>Fri, 15 Aug 2008 20:39:05 +0000</pubDate>
		<dc:creator>Maarten</dc:creator>
				<category><![CDATA[RTE]]></category>
		<category><![CDATA[Snippets]]></category>
		<category><![CDATA[TSConfig]]></category>
		<category><![CDATA[Configuration]]></category>

		<guid isPermaLink="false">http://blog.mmwebdesign.eu/?p=8</guid>
		<description><![CDATA[Here is my default TSConfig configuration for the htmlAREA RTE. I use this one in combination with a typical (default) configuration in the Extension Manager with images enabled. #----------------------------------- # RTE Configuration #----------------------------------- RTE.default { ## Custom client CSS for same behavoir in BE and FE # contentCSS = fileadmin/..... hideTableOperationsInToolbar = 1 buttons.toggleborders.keepInToolbar = [...]]]></description>
			<content:encoded><![CDATA[<p>Here is my default TSConfig configuration for the htmlAREA RTE. I use this one in combination with a typical (default) configuration in the Extension Manager with images enabled.<br />
<span id="more-8"></span></p>
<pre>
#-----------------------------------
# RTE Configuration
#-----------------------------------

RTE.default {

    ## Custom client CSS for same behavoir in BE and FE
    # contentCSS = fileadmin/.....

    hideTableOperationsInToolbar = 1
    buttons.toggleborders.keepInToolbar = 1
    showButtons (
	bold, italic, underline,
	left, center, right, justifyfull,
	orderedlist, unorderedlist,
	line, link, image,
	table, findreplace, chMode,
	copy, cut, paste, undo, redo, toggleborders,
	tableproperties, rowproperties, rowinsertabove,
	rowinsertunder, rowdelete, rowsplit,
	columninsertbefore, columninsertafter,
	columndelete, columnsplit, cellproperties,
	cellinsertbefore, cellinsertafter,
	celldelete, cellsplit, cellmerge
    )
    toolbarOrder (
	bold, italic, underline,
	left, center, right, justifyfull,
	orderedlist, unorderedlist,
	line, link, image,
	table, findreplace, chMode,
	copy, cut, paste, undo, redo, toggleborders,
	tableproperties, rowproperties, rowinsertabove,
	rowinsertunder, rowdelete, rowsplit,
	columninsertbefore, columninsertafter,
	columndelete, columnsplit, cellproperties,
	cellinsertbefore, cellinsertafter,
	celldelete, cellsplit, cellmerge
   )

   proc {
	## CSS Styled Content is used.
	overruleMode = ts_css

	## Do not convert br to p
	dontConvBRtoParagraph = 1

	## Remap div to p
	remapParagraphTag = p

	## Tag which are allowed outside the p and div
	allowTagsOutside = hr, address

	## TAGS ALLOWED
	## Added to the default internal list: b,i,u,a,img,br,div,center,pre,font,hr,sub,sup,p,strong,em,li,ul,ol,blockquote,strike,span
	## But, for the sake of clarity, we use a complete list in alphabetic order.
	## center, font, strike, sdfield and  u will be removed on entry (see below).
	## b and i will be remapped on exit (see below).
	## Note that the link accessibility feature of htmlArea RTE does insert img tags.
	allowTags (
		a, abbr, acronym, address, blockquote, b, br, caption, cite, code, div, em,
		h1, h2, h3, h4, h5, h6, hr, i, img, li, link, ol, p, pre, q, sdfield,
		span, strong, sub, sup, table, tbody, td, th, tr, tt, ul
	)

	## TAGS DENIED
	## Make sure we can set rules on any tag listed in allowTags.
	denyTags >

	## ALLOWED P &#038; DIV ATTRIBUTES
	## Attributes class and align are always preserved
	## Align attribute will be unset on entry (see below)
	## This is a list of additional attributes to keep
	keepPDIVattribs = xml:lang

	## CONTENT TO DATABASE
	entryHTMLparser_db = 1
	entryHTMLparser_db {
		## TAGS ALLOWED
		## Always use the same list of allowed tags.
		allowTags < RTE.default.proc.allowTags

		## TAGS DENIED
		## Make sure we can set rules on any tag listed in allowTags.
		denyTags >

		## AVOID CONTENT BEING HSC'ed TWICE
		htmlSpecialChars = 0

		tags {
			## REMOVE IMG TAGS
			# img.allowedAttribs = 0
			# img.rmTagIfNoAttrib = 1

			## REMOVE SPAN TAGS
			span.allowedAttribs = 0
			span.rmTagIfNoAttrib = 1

			## CLEAN ATTRIBUTES ON THE FOLLOWING TAGS
			## Span fixAttrib unnessesary since not allowed.
			#span.fixAttrib.style.unset = 1
			p.fixAttrib.align.unset = 1
			div.fixAttrib.align.unset = 1
			hr.allowedAttribs = class
			b.allowedAttribs = xml:lang
			blockquote.allowedAttribs = xml:lang
			cite.allowedAttribs = xml:lang
			em.allowedAttribs = xml:lang
			i.allowedAttribs = xml:lang
			q.allowedAttribs = xml:lang
			strong.allowedAttribs = xml:lang
			sub.allowedAttribs = xml:lang
			sup.allowedAttribs = xml:lang
			tt.allowedAttribs = xml:lang
		}

		## REMOVE OPEN OFFICE META DATA TAGS AND DEPRECATED HTML TAGS
		## We use this rule instead of the denyTags rule so that we can
		## protect custom tags without protecting these unwanted tags.
		removeTags = center, font, o:p, sdfield, strike, u

		## PROTECT CUSTOM TAGS
		keepNonMatchedTags = protect
	}

	HTMLparser_db {
		## STRIP ALL ATTRIBUTES FROM THESE TAGS
		## If this list of tags is not set, it will default to: b,i,u,br,center,hr,sub,sup,strong,em,li,ul,ol,blockquote,strike.
		## However, we want to keep xml:lang attribute on most tags and tags from the default list where cleaned on entry.
		noAttrib = br

		## XHTML COMPLIANCE
		## Note that applying xhtml_cleaning on exit would break non-standard attributes of typolink tags
		xhtml_cleaning = 1
	}

	exitHTMLparser_db = 1
	exitHTMLparser_db {
		## REMAP B AND I TAGS
		## b and i tags are used by Mozilla/Firefox in editing mode.
		## This must be done on exit because the default HTMLparser_db parsing executes the reverse mapping.
		tags.b.remap = strong
		tags.i.remap = em

		## KEEP ALL TAGS
		## Unwanted tags were removed on entry.
		## Without this rule, the parser will remove all tags! Presumably, this rule will be more efficient than repeating the allowTags rule
		keepNonMatchedTags = 1

		## AVOID CONTENT BEING HSC'ed TWICE
		htmlSpecialChars = 0
	}
   }
}

## Use same RTE processing rules in FE
RTE.default.FE.proc < RTE.default.proc

## RTE processing rules for bodytext column of tt_content table
## Erase settings from other extensions
RTE.config.tt_content.bodytext >

## Make sure we use ts_css transformation
RTE.config.tt_content.bodytext.proc.overruleMode = ts_css
RTE.config.tt_content.bodytext.types.text.proc.overruleMode = ts_css
RTE.config.tt_content.bodytext.types.textpic.proc.overruleMode = ts_css</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.typo3-addict.com/2008/08/my-default-rte-configuration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TYPO3: RTE Full screen button</title>
		<link>http://www.typo3-addict.com/2008/08/rte-full-screen-button/</link>
		<comments>http://www.typo3-addict.com/2008/08/rte-full-screen-button/#comments</comments>
		<pubDate>Thu, 07 Aug 2008 20:25:17 +0000</pubDate>
		<dc:creator>Maarten</dc:creator>
				<category><![CDATA[RTE]]></category>
		<category><![CDATA[Snippets]]></category>
		<category><![CDATA[TSConfig]]></category>

		<guid isPermaLink="false">http://blog.mmwebdesign.eu/?p=3</guid>
		<description><![CDATA[Normally, when you hit the full screen button in the htmlAREA RTE, the text-area doesn&#8217;t go full screen at all. Instead most of the time (depending on your browser and TYPO3 version) you&#8217;ll get this half full screen text area which is really not helpful at all. To fix this, past to following line into [...]]]></description>
			<content:encoded><![CDATA[<p>Normally, when you hit the full screen button in the htmlAREA RTE, the text-area doesn&#8217;t go full screen at all. Instead most of the time (depending on your browser and TYPO3 version) you&#8217;ll get this half full screen text area which is really not helpful at all.  To fix this, past to following line into your TSConfig field in the parent page or folder.</p>
<pre lang='css'>
TCEFORM.tt_content.bodytext.RTEfullScreenWidth = 100%
</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.typo3-addict.com/2008/08/rte-full-screen-button/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

