<?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; Configuration</title>
	<atom:link href="http://www.typo3-addict.com/tag/configuration/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.typo3-addict.com</link>
	<description>For those addicted to TYPO3</description>
	<lastBuildDate>Wed, 02 Jun 2010 13:03:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>TYPO3: Hide records from static_info_tables in the rootpage</title>
		<link>http://www.typo3-addict.com/2010/05/hide-records-from-static_info_tables-in-the-rootpage/</link>
		<comments>http://www.typo3-addict.com/2010/05/hide-records-from-static_info_tables-in-the-rootpage/#comments</comments>
		<pubDate>Wed, 05 May 2010 08:50:26 +0000</pubDate>
		<dc:creator>Maarten</dc:creator>
				<category><![CDATA[Snippets]]></category>
		<category><![CDATA[TSConfig]]></category>
		<category><![CDATA[Configuration]]></category>

		<guid isPermaLink="false">http://blog.mmwebdesign.eu/?p=70</guid>
		<description><![CDATA[After you installed static_info_tables in your TYPO3 installtion, you get a whole bunch of records displayed in the rootpage. This really slows down the page, which isn&#8217;t funny when you work a lot with usergroups. You can hide all of these records with a simple line in your BE-User-TSConfig. Insert the following User TSConfig into [...]]]></description>
			<content:encoded><![CDATA[<p>After you installed static_info_tables in your TYPO3 installtion, you get a whole bunch of records displayed in the rootpage. This really slows down the page, which isn&#8217;t funny when you work a lot with usergroups. You can hide all of these records with a simple line in your BE-User-TSConfig.<span id="more-70"></span></p>
<p>Insert the following User TSConfig into your own userrecord or in the usergroup to which you belong (i.e. Admins).</p>
<pre>mod.web_list.hideTables=static_template, static_countries,
static_country_zones, static_currencies, static_languages,
static_territories, static_taxes, static_markets</pre>
<p><strong>IMPORTANT:</strong><br />
I had to use spaces in the code above in order to display it right. DON&#8217;T use them in your TSConfig!</p>
<p><!-- .googleAdsenseTop {  display: none; } --></p>
]]></content:encoded>
			<wfw:commentRss>http://www.typo3-addict.com/2010/05/hide-records-from-static_info_tables-in-the-rootpage/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>TYPO3: 5 things about tt_news</title>
		<link>http://www.typo3-addict.com/2009/10/5-things-you-should-know-about-tt_news/</link>
		<comments>http://www.typo3-addict.com/2009/10/5-things-you-should-know-about-tt_news/#comments</comments>
		<pubDate>Fri, 16 Oct 2009 07:32:22 +0000</pubDate>
		<dc:creator>Maarten</dc:creator>
				<category><![CDATA[Extensions]]></category>
		<category><![CDATA[Snippets]]></category>
		<category><![CDATA[Configuration]]></category>
		<category><![CDATA[GIFBUILDER]]></category>
		<category><![CDATA[tt_news]]></category>
		<category><![CDATA[Typoscript]]></category>

		<guid isPermaLink="false">http://www.typo3-addict.com/?p=610</guid>
		<description><![CDATA[In this post I'll show you 5 things about tt_news which might be nice to know about tt_news. We discuss a better pagebrowser, loading tt_news without cache and making images perfectly square by generating them automatically.]]></description>
			<content:encoded><![CDATA[<p>The tt_news extension is the most popular extension of TYPO3. No wonder, since it&#8217;s very flexible and can be used for much more than just handling newsitems. In this post I&#8217;ll show you 5 things about tt_news which might be nice to know about tt_news.</p>
<h4>1) A better pagebrowser</h4>
<p>By default, the tt_news pagebrowser is not very nice. Nor can it be easily styled. Inside tt_news there&#8217;s a &#8216;hidden&#8217; pagebrowser which is better, and much more flexible. To activate this better pagebrowser put the following into your template Setup section:<br />
<span id="more-610"></span></p>
<pre>#-----------------------------------
# A better tt_news pagebrowser
#-----------------------------------

plugin.tt_news {
  usePiBasePagebrowser = 1     # This activates the better pagebrowser
  pageBrowser {                # Here you can configure the better pagebrowser
    maxPages = 7                  # Maximum browserpage links
    showResultCount = 1           # Display the sentence: ** till ** out of ** messages
    showRange = 1                 # Will look like "Items: <span style="text-decoration: underline;">1-5</span> <span style="text-decoration: underline;">6-10</span>" instead of "Page <span style="text-decoration: underline;">1</span> <span style="text-decoration: underline;">2</span> <span style="text-decoration: underline;">3</span> <span style="text-decoration: underline;">4</span>"
    showPBrowserText = 0          # Prepends "<span style="text-decoration: underline;">1</span> <span style="text-decoration: underline;">2</span> <span style="text-decoration: underline;">3</span>" like "<span style="text-decoration: underline;">page 1</span> <span style="text-decoration: underline;">page 2</span> <span style="text-decoration: underline;">page 3</span>", only when showRange = 0
    dontLinkActivePage = 1        # No need to link the active page
    showFirstLast = 0             # Show a first / last link, 0 since there already is a previous / next link.
  }
}

#-----------------------------------
# Locallang for the tt_news pagebrowser
#-----------------------------------

plugin.tt_news {
  _LOCAL_LANG.default {
    pi_list_browseresults_displays = Newsitem ###FROM### till ###TO### out of ###OUT_OF### newsitems.
    pi_list_browseresults_first = First page
    pi_list_browseresults_last = Last page
    pi_list_browseresults_page = Page
    pi_list_browseresults_prev = &lt; Previous
    pi_list_browseresults_next = Next &gt;
  }
}</pre>
<h4>2) Do not display duplicate items</h4>
<p>If you have more than one tt_news plugin on your page, this can be nice. For example: The first plugin only shows the last newsitem, the second plugin the 5 most recent newsitems. The most recent newsitem is now shown by both the plugins. You can tell tt_news to only show newsitems once. This only works for List mode plugins. Put the following lines into your template Setup section:</p>
<pre>#-----------------------------------
# Only show newsitems once per page.
#-----------------------------------

plugin.tt_news {
  excludeAlreadyDisplayedNews = 1
}</pre>
<p>If &#8220;excludeAlreadyDisplayedNews&#8221; is enabled &#8220;excludeLatestFromList&#8221; and &#8220;listStartId&#8221; will be ignored. This is no problem, since both these fields are deprecated. Be aware this might break your archive links.</p>
<h4>3) Generate a tt_news image automatically when no image is available</h4>
<p>If your template design forces you to upload a photo with every newsitem, this can be helpful. The following code will generate a &#8220;No image&#8221; image using GIFBUILDER. Put this code in your template Setup section:</p>
<pre>#-----------------------------------
# Generate a tt_news image automatically when no image is available.
# In this snippet: Latest mode
#-----------------------------------

plugin.tt_news.displayLatest.image.noImage_stdWrap {
  cObject = IMAGE
  cObject {
    # Wrap the image with a div tag
    wrap = &lt;div&gt;|&lt;/div&gt;
    # Use GIFBUILDER to create an image
    file = GIFBUILDER
    file {
      # Define the width and height of the image.
      XY = 125,125
      # Define the background color of the image.
      backColor = #FFFFFF

      # First object in the image: TEXT
      10 = TEXT
      10 {
        # The actual text which is displayed in the image
        text = No image available
        # The fontsize
        fontSize = 16
        # niceText to make the text more natural. This can be good or bad depending on your server configuration.
        niceText = 1
        # Color of the text
        fontColor = #000000
        # Coordinates where your text should appear in the image. Width / Height
        offset = 125/2-32,125/2+4
      }
    }
  }
}</pre>
<h4>4) Load tt_news without cache; for example random news.</h4>
<p>If you want to display newsrecords random, set the viewmode to LIST or LATEST and set the &#8217;order by&#8217; field to &#8216;randomise order&#8217;. The tricky part here is that your plugin shouldn&#8217;t be cached, since that would destroy the whole random idea. Ofcourse you can set the whole page to &#8216;no cache&#8217; but this would kill your performance. Better is to just tell tt_news to use no cache. It will still cost you some performance but, it&#8217;s better than not caching the whole page. To setup tt_news without cache put the following code  into your template Setup section:</p>
<pre>#-----------------------------------
# Run tt_news without cache, remember to unset in deeper levels!
#-----------------------------------

plugin.tt_news = USER_INT</pre>
<p>This will load the tt_news plugin as a USER_INT object and render it without cache, outside of the main pagerendering. This way your page will be called from cache but the plugin will be non-cached. Just be sure to un-set this rendering on a deeper pagelevel since TypoScript is inherited from levels above.</p>
<h4>5) Perfectly square tt_news images.</h4>
<p>By default tt_news allows you to set the maximum width and height for an image in LIST or LATEST mode. Width and height are adjusted automatically when one exceeds the other. But what if you want a perfectly square image no matter what photo is being uploaded? CSS seems to be the only way to do this but there&#8217;s a solution which is better..</p>
<p>Ever noticed TYPO3 is able to crop images as soon as resizing isn&#8217;t posible anymore? An example: we have an image of 400 x 300 pixels, we want a picture of 30 x 30. What it does is it resizes the image to 40 x 30 pixels and than crops the width to 30 pixels. But that&#8217;s TYPO3.. not tt_news.</p>
<p>To enable this for tt_news you need to put the following code into your tempate Setup section:</p>
<pre>#-----------------------------------
# Generate a perfectly square tt_news image.
# In this snippet: Latest mode
#-----------------------------------

plugin.tt_news {
    # This only affects the LATEST mode, to use LIST mode change to 'displayList'
    displayLatest {
        # Unset the default tt_news maximum width and height parameter
        image.file.maxW &gt;
        image.file.maxH &gt;
        # Call the TYPO3 way to render images, setting it to 90 pixels; cropping mode (c)
        image.file.width  = 90c
        image.file.height = 90c
        # Make the images SEO, using the caption as Alt tag.
        image.altText.field = imagecaption
    }
}</pre>
<p>Now, the image will be resized untill the given width or height is reached and than be cropped. Width and height are always in pixels so there is no need to append &#8216;px&#8217;. The &#8216;c&#8217; tells TYPO3 to crop the image.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.typo3-addict.com/2009/10/5-things-you-should-know-about-tt_news/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TYPO3 SEO: The Basics&#8230;</title>
		<link>http://www.typo3-addict.com/2009/10/typo3-seo-the-basics/</link>
		<comments>http://www.typo3-addict.com/2009/10/typo3-seo-the-basics/#comments</comments>
		<pubDate>Sun, 11 Oct 2009 12:10:19 +0000</pubDate>
		<dc:creator>Maarten</dc:creator>
				<category><![CDATA[Extensions]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[Snippets]]></category>
		<category><![CDATA[Configuration]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[Sourcecode]]></category>
		<category><![CDATA[Typoscript]]></category>

		<guid isPermaLink="false">http://www.typo3-addict.com/?p=556</guid>
		<description><![CDATA[In this post I'm going to show you some basics of SEO in TYPO3, I will explain how you can easily handle SEO stuff within TYPO3. This is not a "best practise" nor is it a tutorial on how SEO works. But if you're new to TYPO3, or SEO in TYPO3 you'll find some useful things here.]]></description>
			<content:encoded><![CDATA[<p>In this post I&#8217;m going to show you some basics of SEO in TYPO3, I will explain how you can easily handle SEO stuff within TYPO3. This is not a &#8220;best practise&#8221; nor is it a tutorial on how SEO works. But if you&#8217;re new to TYPO3, or SEO in TYPO3 you&#8217;ll find some useful things here.</p>
<h4>Basic no. 1: A clean source code.</h4>
<p>A clean source code makes it easier for search engines to crawl your website. For that, you need to clean up the default HTML output done by TYPO3. Use this line of TypoScript a put it in your template Setup section:<span id="more-556"></span></p>
<pre># Clean up prefixes in source code
config.disablePrefixComment = 1</pre>
<p>This will clean up the prefixes made with every content-element. This should be a relief! For a more complete cleanup please <a title="Clean up your sourcecode!" href="http://www.typo3-addict.com/2009/02/updated-cleanup-your-fe-sourcecode/">go to this post</a>.</p>
<h4>Basic no. 2: Make you headers better.</h4>
<p>By default, every content-element header is a &lt;h1&gt; header in TYPO3. For your SEO it&#8217;s better to just have one &lt;h1&gt; tag per page. To convert all these &lt;h1&gt; tags into &lt;h2&gt; tags you need to put the following line in your template Constants section:</p>
<pre># Convert default H1 tags into H2 tags
content.defaultHeaderType = 2</pre>
<p>You can now add a &lt;h1&gt; tag manually to the page, or generate one dynamically using TypoScript.</p>
<h4>Basic no. 3: Images.</h4>
<p>By default, images which are scaled, croped or in any other way modified by TYPO3 are given a random name. For example:</p>
<pre>/typo3temp/pics/b3e43c4bb3.jpg.</pre>
<p>By installing the extension: <a title="Nicer image names" href="http://typo3.org/extensions/repository/view/fl_realurl_image/current/">fl_realurl_image</a>, your images will get a nicer name. Install the extension and you&#8217;re done. Images will now be named like:</p>
<pre>/typo3temp/fl_realurl_image/your_image.jpg</pre>
<h4>Basic no. 4: Page title.</h4>
<p>The pagetitle is important for your SEO ranking. This title needs to summerize the pagecontent as close as posible. I suggest you manually edit these to your needs. Someone (can&#8217;t rememer the name, sorry) once told me: Use an inverted breadcrumb path as a pagetitle. The theory behind this: People think about their page names, the lower in the pagetree the more specific. If you invert this you have a pretty close to content path and also the main keywords which people interested in this subject will search for.</p>
<h4>Basic no. 5: URL&#8217;s.</h4>
<p>The default URL&#8217;s of TYPO3 are not readable, the solution to this problem is RealURL. Since this extension is really popular I&#8217;m not going to explain it, this has been done more than enough times. Just search the web for a good tutorial. I can recommend the extension &#8220;danp_realurlconfigurator&#8221; though, which gives you a nice configurator.</p>
<h4>Basic no. 6: Description and meta tags.</h4>
<p>A really important SEO rule is to have unique page descriptions and meta tags. Since these fields have to match the page content as close as posible it&#8217;s only logical to have them in your page configuration. If you edit your page you&#8217;ll find the second tab is all about meta data. Here you can fill in the description and meta tags for your page. To actually use these field in the frontend source code you&#8217;ll need to following lines in your template Setup section:</p>
<pre># This will activate the page meta data
page.meta.keywords.field = keywords
page.meta.description.field = description</pre>
<h4>Basic no. 7: An XML sitemap for Google Webmaster Center.</h4>
<p>If you want Google to track your page changes and crawl them accordingly you can submit a XML sitemap. If you do not know what a XML sitemap is <a title="Google Sitemaps" href="http://www.google.com/support/webmasters/bin/answer.py?hl=en&amp;answer=82300">please read this first</a>. There are a couple of extensions to generate such a sitemap dynamically in TYPO3.</p>
<h4>Basic no. 8: JavaScript at the bottom of your source.</h4>
<pre>Deprecated since version 4.3! Use page.includeJSFooter instead.</pre>
<p>This might be more of a speed thing rather than SEO, but still&#8230; By default TYPO3 will put javascript includes in your header.</p>
<pre>-- SNIP: Deprecated snippet --</pre>
<p>TYPO3 also generates a default JavaScript which can be removed by putting this line in your template Setup section:</p>
<pre># Remove the default JS file in the header
config.removeDefaultJS = 1</pre>
<p>Make sure you copy the content of this file to your custom one before removing it.</p>
<h4>Tip: Extension <a title="Seo_Basics extension" href="http://typo3.org/extensions/repository/view/seo_basics/current/">seo_basics</a></h4>
<p style="text-align: left;">Benjamin Mack has developed an extension (<a title="Seo_Basics extension" href="http://typo3.org/extensions/repository/view/seo_basics/current/">seo_basics)</a> which is really useful. It not only generates the XML sitemap by default, but it also helps you to update the page descriptions and meta tags. Download and install the extension through the extension manager. Once installed, go to http://www.your-website.com/sitemap.xml, you&#8217;ll notice it works right out of the box. (If it doesn&#8217;t, please check you RealURL configuration). But this is just the beginning. Go to the &#8220;info&#8221; module and select your root website page. Now, in the drop-down box choose &#8220;SEO Management&#8221;.</p>
<p>(Update: 17-01-2010: Breaking change in extension update, include static template first!)</p>
<div id="attachment_569" class="wp-caption aligncenter" style="width: 600px"><a href="http://www.typo3-addict.com/wp-content/uploads/2009/10/seo_basics_11.png"><img class="size-full wp-image-569 " title="Seo Basics: Screen 1" src="http://www.typo3-addict.com/wp-content/uploads/2009/10/seo_basics_11.png" alt="Click to enlarge!" width="590" /></a><p class="wp-caption-text">Click to enlarge!</p></div>
<p style="text-align: left;">Here you&#8217;ll see all pages with there url-path, title, description and metatags. Click on the &#8220;Edit SEO fields&#8221;. Now you&#8217;ll notice you can edit all fields of all pages within one screen! Once you start filling in the details you&#8217;ll notice the color changes while typing:</p>
<p style="text-align: left;">Yellow: To little text<br />
Green: Just good!<br />
Red: To much text</p>
<p>If you would like to add META Abstract &amp; Author to seo_basics please look at this post of Michael Cannon: <a href="http://www.acqal.com/blog/a/article/add-meta-abstract-author-to-seo-basics/">http://www.acqal.com/blog/a/article/add-meta-abstract-author-to-seo-basics/</a></p>
<div id="attachment_570" class="wp-caption aligncenter" style="width: 600px"><a href="http://www.typo3-addict.com/wp-content/uploads/2009/10/seo_basics_2.png"><img class="size-full wp-image-570 " title="seo_basics_2" src="http://www.typo3-addict.com/wp-content/uploads/2009/10/seo_basics_2.png" alt="Click to enlarge!" width="590" /></a><p class="wp-caption-text">Click to enlarge!</p></div>
<h4>Hope you liked this post:)</h4>
<p>These basics are far from a complete reference but I hope they will be of use. If you&#8217;ve got suggestions, please don&#8217;t hesitate to comment&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.typo3-addict.com/2009/10/typo3-seo-the-basics/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>TYPO3: Javascript at the bottom of your page</title>
		<link>http://www.typo3-addict.com/2009/01/javascript-at-the-bottom-of-your-page/</link>
		<comments>http://www.typo3-addict.com/2009/01/javascript-at-the-bottom-of-your-page/#comments</comments>
		<pubDate>Tue, 06 Jan 2009 11:00:39 +0000</pubDate>
		<dc:creator>Maarten</dc:creator>
				<category><![CDATA[Snippets]]></category>
		<category><![CDATA[Configuration]]></category>
		<category><![CDATA[Speed]]></category>
		<category><![CDATA[Typoscript]]></category>

		<guid isPermaLink="false">http://blog.emaux.nl/?p=225</guid>
		<description><![CDATA[Yslow tells you to put your javascripts at the bottom of your pages. Normally when you include your JS files TYPO3 puts them in your head by default. To fix this you can easily: Old style: page.includeJS.file1 = file.js Solution: page.20 &#60; lib.javascript lib.javascript = HTML lib.javascript.value = &#60;script type="text/javascript" src="file.js"&#62;&#60;/script&#62; Note: In this example [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://developer.yahoo.com/yslow/">Yslow</a> tells you to put your javascripts at the bottom of your pages. Normally when you include your JS files TYPO3 puts them in your head by default. To fix this you can easily:</p>
<p><strong>Old style:</strong></p>
<pre lang="css">page.includeJS.file1 = file.js</pre>
<p><strong>Solution:</strong></p>
<pre lang="css">page.20 &lt; lib.javascript

lib.javascript = HTML
lib.javascript.value = &lt;script type="text/javascript" src="file.js"&gt;&lt;/script&gt;</pre>
<p><strong>Note:</strong></p>
<p>In this example I take it your content is in page.10<br />
If you already use page.20 than just take a higher value.</p>
<p>It&#8217;s not posible (as far as I know) to put the default js at the bottom, this is core stuff.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.typo3-addict.com/2009/01/javascript-at-the-bottom-of-your-page/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>TYPO3: The Clipboard</title>
		<link>http://www.typo3-addict.com/2009/01/the-clipboard/</link>
		<comments>http://www.typo3-addict.com/2009/01/the-clipboard/#comments</comments>
		<pubDate>Sun, 04 Jan 2009 06:30:18 +0000</pubDate>
		<dc:creator>Maarten</dc:creator>
				<category><![CDATA[TSConfig]]></category>
		<category><![CDATA[Configuration]]></category>

		<guid isPermaLink="false">http://blog.emaux.nl/?p=221</guid>
		<description><![CDATA[The TYPO3 clipboard is a very handy tool but you rarely use all 4 of them. Also, when you logout the content is gone. Both these things can be fixed by a little TSConfig: ## Makes sure the clipboard doesn't clear: options.saveClipboard = 1 ## Reduces the amount of clipboards from 4 to 1: options.clipboardNumberPads [...]]]></description>
			<content:encoded><![CDATA[<p>The TYPO3 clipboard is a very handy tool but you rarely use all 4 of them. Also, when you logout the content is gone. Both these things can be fixed by a little TSConfig:</p>
<pre lang="css">
## Makes sure the clipboard doesn't clear:
options.saveClipboard = 1

## Reduces the amount of clipboards from 4 to 1:
options.clipboardNumberPads = 1
</pre>
<p>If ANYONE know how to use copy as default instead of move a comment is highly appreciated!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.typo3-addict.com/2009/01/the-clipboard/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TYPO3: Wider text field in BE</title>
		<link>http://www.typo3-addict.com/2008/11/wider-text-field-in-be/</link>
		<comments>http://www.typo3-addict.com/2008/11/wider-text-field-in-be/#comments</comments>
		<pubDate>Sun, 16 Nov 2008 19:24:50 +0000</pubDate>
		<dc:creator>Maarten</dc:creator>
				<category><![CDATA[Snippets]]></category>
		<category><![CDATA[TSConfig]]></category>
		<category><![CDATA[Configuration]]></category>

		<guid isPermaLink="false">http://blog.emaux.nl/?p=128</guid>
		<description><![CDATA[I just found this line in the TSRef.. It&#8217;s not perfect but it makes your BE field like setup and constants in list mode wider. Just a small User TSConfig line so why not&#8230; ## Makes the BE fields wider setup.override.edit_wideDocument = 1 See screenshots!]]></description>
			<content:encoded><![CDATA[<p>I just found this line in the TSRef.. It&#8217;s not perfect but it makes your BE field like setup and constants in list mode wider. Just a small User TSConfig line so why not&#8230;</p>
<pre style="text-align: left;">
## Makes the BE fields wider
setup.override.edit_wideDocument = 1
</pre>
<p>See screenshots!</p>
<p><span id="more-128"></span></p>
<div id="attachment_129" class="wp-caption alignnone" style="width: 249px"><a href="http://blog.emaux.nl/wp-content/uploads/2008/11/afbeelding-2.png"><img class="size-medium wp-image-129" title="BE_Fields_normal" src="http://blog.emaux.nl/wp-content/uploads/2008/11/afbeelding-2-239x300.png" alt="Backend Field without TSConfig line" width="239" height="300" /></a><p class="wp-caption-text">Backend Field without TSConfig line</p></div>
<div id="attachment_130" class="wp-caption alignnone" style="width: 310px"><a href="http://blog.emaux.nl/wp-content/uploads/2008/11/afbeelding-3.png"><img class="size-medium wp-image-130" title="BE_Field_TSConfig" src="http://blog.emaux.nl/wp-content/uploads/2008/11/afbeelding-3-300x279.png" alt="Backend Field with TSConfig line" width="300" height="279" /></a><p class="wp-caption-text">Backend Field with TSConfig line</p></div>
]]></content:encoded>
			<wfw:commentRss>http://www.typo3-addict.com/2008/11/wider-text-field-in-be/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TYPO3: Alternative BE Backgroundcolor</title>
		<link>http://www.typo3-addict.com/2008/11/alternative-be-backgroundcolor/</link>
		<comments>http://www.typo3-addict.com/2008/11/alternative-be-backgroundcolor/#comments</comments>
		<pubDate>Fri, 14 Nov 2008 13:41:15 +0000</pubDate>
		<dc:creator>Maarten</dc:creator>
				<category><![CDATA[Snippets]]></category>
		<category><![CDATA[TSConfig]]></category>
		<category><![CDATA[Configuration]]></category>

		<guid isPermaLink="false">http://blog.mmwebdesign.eu/?p=96</guid>
		<description><![CDATA[The following Page TSConfig line is usefull if you have a lot of records on a single page. mod.web_list { alternateBgColors = 1 }]]></description>
			<content:encoded><![CDATA[<p>The following Page TSConfig line is usefull if you have a lot of records on a single page.</p>
<pre>mod.web_list {
  alternateBgColors = 1
}</pre>
<p><span id="more-96"></span></p>
<div id="attachment_124" class="wp-caption alignnone" style="width: 310px"><a href="http://blog.emaux.nl/wp-content/uploads/2008/11/afbeelding-1.png"><img class="size-medium wp-image-124" title="be_bg_color" src="http://blog.emaux.nl/wp-content/uploads/2008/11/afbeelding-1-300x123.png" alt="Every other line an other color" width="300" height="123" /></a><p class="wp-caption-text">Every other line an other color</p></div>
]]></content:encoded>
			<wfw:commentRss>http://www.typo3-addict.com/2008/11/alternative-be-backgroundcolor/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TYPO3: Disable hide &amp; prepend at copy</title>
		<link>http://www.typo3-addict.com/2008/11/disable-hide-prepend-at-copy/</link>
		<comments>http://www.typo3-addict.com/2008/11/disable-hide-prepend-at-copy/#comments</comments>
		<pubDate>Fri, 07 Nov 2008 13:13:53 +0000</pubDate>
		<dc:creator>Maarten</dc:creator>
				<category><![CDATA[Snippets]]></category>
		<category><![CDATA[TSConfig]]></category>
		<category><![CDATA[Configuration]]></category>

		<guid isPermaLink="false">http://blog.mmwebdesign.eu/?p=93</guid>
		<description><![CDATA[Personally I hate it when TYPO3 hides my new copied record. TYPO3 also prepends your new copied record with something like &#8216;copy (1)&#8217;. To avoid this you can put this code in your PageTSConfig: TCEMAIN.table.pages { disablePrependAtCopy = 1 disableHideAtCopy = 1 } TCEMAIN.table.tt_content { disablePrependAtCopy = 1 disableHideAtCopy = 1 }]]></description>
			<content:encoded><![CDATA[<p>Personally I hate it when TYPO3 hides my new copied record. TYPO3 also prepends your new copied record with something like &#8216;copy (1)&#8217;. To avoid this you can put this code in your PageTSConfig:</p>
<pre>TCEMAIN.table.pages {
  disablePrependAtCopy = 1
  disableHideAtCopy = 1
}

TCEMAIN.table.tt_content {
  disablePrependAtCopy = 1
  disableHideAtCopy = 1
}</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.typo3-addict.com/2008/11/disable-hide-prepend-at-copy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TYPO3: Clean up non used tt_content fields</title>
		<link>http://www.typo3-addict.com/2008/11/clean-up-non-used-tt_content-fields/</link>
		<comments>http://www.typo3-addict.com/2008/11/clean-up-non-used-tt_content-fields/#comments</comments>
		<pubDate>Sat, 01 Nov 2008 13:10:16 +0000</pubDate>
		<dc:creator>Maarten</dc:creator>
				<category><![CDATA[Snippets]]></category>
		<category><![CDATA[TSConfig]]></category>
		<category><![CDATA[Configuration]]></category>

		<guid isPermaLink="false">http://blog.mmwebdesign.eu/?p=91</guid>
		<description><![CDATA[In most cases I don&#8217;t use some tt_content fields, so it would be nice to don&#8217;t see them at all. Also for other backend users less is more (easy).  So let&#8217;s clean them up! Copy Paste this in your Page TSConfig: #----------------------------------- # Clean up tt_content #----------------------------------- TCEFORM.tt_content.section_frame.disabled = 1 TCEFORM.tt_content.date.disabled = 1 TCEFORM.tt_content.linkToTop.disabled = [...]]]></description>
			<content:encoded><![CDATA[<p>In most cases I don&#8217;t use some tt_content fields, so it would be nice to don&#8217;t see them at all. Also for other backend users less is more (easy).  So let&#8217;s clean them up!</p>
<p><span id="more-91"></span>Copy Paste this in your Page TSConfig:</p>
<pre>#-----------------------------------
# Clean up tt_content
#-----------------------------------

TCEFORM.tt_content.section_frame.disabled = 1
TCEFORM.tt_content.date.disabled = 1
TCEFORM.tt_content.linkToTop.disabled = 1
TCEFORM.tt_content.header_position.disabled = 1
TCEFORM.tt_content.rte_enabled.disabled = 1
TCEFORM.tt_content.longdescURL.disabled = 1
TCEFORM.tt_content.altText.disabled = 1
TCEFORM.tt_content.image_effects.disabled = 1
TCEFORM.tt_content.image_compression.disabled = 1
TCEFORM.tt_content.imagecaption_position.disabled = 1
TCEFORM.tt_content.titleText.disabled = 1
TCEFORM.tt_content.sectionIndex.disabled = 1</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.typo3-addict.com/2008/11/clean-up-non-used-tt_content-fields/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TYPO3: Removing content element columns</title>
		<link>http://www.typo3-addict.com/2008/10/removing-content-columns/</link>
		<comments>http://www.typo3-addict.com/2008/10/removing-content-columns/#comments</comments>
		<pubDate>Sat, 25 Oct 2008 13:03:02 +0000</pubDate>
		<dc:creator>Maarten</dc:creator>
				<category><![CDATA[Snippets]]></category>
		<category><![CDATA[TSConfig]]></category>
		<category><![CDATA[Configuration]]></category>

		<guid isPermaLink="false">http://blog.mmwebdesign.eu/?p=88</guid>
		<description><![CDATA[Sometimes you need to make the TYPO3 BE as clean and empty as posible for other (read: less techical) users. In that case it can be usefull to remove non-used content columns. Here how to: Copy Paste this in your Page TSConfig TCEFORM.tt_content.colPos { altLabels { 1 = Left 0 = Normal 2 = Right [...]]]></description>
			<content:encoded><![CDATA[<p>Sometimes you need to make the TYPO3 BE as clean and empty as posible for other (read: less techical) users. In that case it can be usefull to remove non-used content c<span class="class-main5">olumns. Here how to:</span></p>
<p>Copy Paste this in your Page TSConfig</p>
<pre>TCEFORM.tt_content.colPos {
  altLabels {
     1 = Left
     0 = Normal
     2 = Right
     3 = Border
  }
  #Remove Right &amp; Border
  removeItems = 2,3
}</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.typo3-addict.com/2008/10/removing-content-columns/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
