Read more for the solution!

How to set the click and enlarge option for the RTE in tt_news:

Step 1:
Include the static template: Clickenlarge Rendering (rtehtmlarea)

Now the click and enlarge rendering should work for normal content elements, but still no result for tt_news.

Step 2:
Add the following TypoScript to your setup:

# 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
        }
}

Your Done :)

It turns out tt_news uses another way of rendering the RTE, so this should be reversed.

Update: It seems this snippet is actually part of the tt_news static template but out-commented... makes me wonder why?

Login Screen

Home sweet home

Content

Insert the following User TSConfig into your own userrecord or in the usergroup to which you belong (i.e. Admins).

mod.web_list.hideTables=static_template, static_countries,
static_country_zones, static_currencies, static_languages,
static_territories, static_taxes, static_markets

IMPORTANT:
I had to use spaces in the code above in order to display it right. DON’T use them in your TSConfig!

I took the Integrator Exam a couple of weeks ago in Brussels, Belgium at the FOSDEM conference. The english e-book version of the original TYPO3 Integrator Exam book (Patrick Lobacher) was a real help. Not only does it help you to prepare for your exam, but the clear and complete answers are also a good way to learn TypoScript by examples. I recommend this book for everyone who works with TypoScript, weather you take the exam or not.

A header with a date attached:

# Overwrite layout 5
# Create an array of objects
lib.stdheader.10.5 = COA
lib.stdheader.10.5 {
   # First object is a copy of the default header layout 1,
   # so the basic input is printed. (e.g. the field 'header')
   10 < lib.stdheader.10.1
   10.fontTag = <h2{register:headerStyle}{register:headerClass}>|

   # Second object: The date which we want to be appended.
   20 = TEXT
   20 {
      data = date:U
      strftime = %A %e %B
   }

   # Third object: Closing the H2 tag which we opened
   # in the first object.
   30 = TEXT
   30.value = </h2>
}

A header with the username

# Overwrite layout 5
# Create an array of objects
lib.stdheader.10.5 = COA
lib.stdheader.10.5 {
   # First object is a copy of the default header layout 1,
   # so the basic input is printed. (e.g. the field 'header')
   10 < lib.stdheader.10.1
   10.fontTag = <h2{register:headerStyle}{register:headerClass}>|

   # Second object: insert the username.
   20 = TEXT
   20.value = {TSFE:fe_user|user|name}
   20.insertData = 1

   # Third object: Closing the H2 tag which we opened
   # in the first object.
   30 = TEXT
   30.value = </h2>
}

GIFBUILDER can’t actually read your headertext so there’s no way it can determine when to use multiple lines by itself (at least, not without making weird cuts in the middle of your words). Therefore, we need to tell GIFBUILDER when to break the line.

Since we only use one H1 tag per seo, this snippet modifies the second header layout.

# Start overriding the second header layout.
lib.stdheader.10.2 >
lib.stdheader.10.2 = COA
lib.stdheader.10.2 {
  # Wrap the whole header
  wrap = <div>|</div>
  10 = IMAGE
  10 {
     # Wrap the first line
     wrap = <div>|</div>
     file = GIFBUILDER
     file {
        XY = [10.w] + 4, [10.h] + 8
        backColor = #FFFFFF
        10 = TEXT
        10 {
           text.field = header
           # Set the fontfile and font-properties.
           fontFile = fileadmin/fonts/customfont.ttf
           fontSize = 22
           fontColor = #000000
           offset = 0,18
           # Select the first line of our sentence.
           text.listNum = 0
           # Here we determine the break, in this case a pipe (|).
           text.listNum.splitChar = |
        }
     }
  }
  # Check if the second line is there...
  20 = COA
  20.if {
     value.field = header
     isTrue.cObject = TEXT
     isTrue.cObject.field = header
     # The second line starts after the pipe
     isTrue.cObject.listNum.splitChar = |
     # Now use the second line of our sentence
     isTrue.cObject.listNum = 1
  }
  # If the second line is there, use the same markup
  20.10 < .10
  20.10 {
     file {
        10.text.listNum = 1
        10.text.listNum.splitChar = |
     }
  }
}

Just to be clear: A header with two lines would now be like:
This is a very long header which will | be displayed over two lines.

Result:

The pipe will be the place where you split the header. Ofcourse, all the font properties used in the first line are also available in the second line, so play all you like with different fonts and markup on every other line.

A condition always consists of 2 brackets with a statement in the middle:

[your-statement]

Multiple conditions can be combined by using so called operators: && (AND) or || (OR), if no operator is defined the default will be OR.

Example 1: Load ie.css only when the browser is IE

[browser = msie]
page.includeCSS {
   1 = fileadmin/ie.css
}
[end]

Example 2: Load ie6.css only when the browser is IE and the version is lower than 7

[browser = msie] && [version = <7]
page.includeCSS {
   1 = fileadmin/ie6.css
}
[end]

Example 3: Load ie stylesheet when the browser is IE, load normal stylesheet with all other browsers

[browser = msie] && [version = <7]
page.includeCSS {
   1 = fileadmin/ie.css
}
[else]
page.includeCSS {
   1 = fileadmin/style.css
}
[end]

Example 4: Use the time to accordingly greet your visitor

# Display 'Good Morning before 12 o'clock
[hour =< 12]
lib.greeting = TEXT
lib.greeting {
    value = Good Morning!
}
[else]
# Display 'Good Day' after 12 o'clock
lib.greeting = TEXT
lib.greeting {
    value = Good Day!
}
[end]

Let’s make things a little bit more interesting.

Example 5: We want to include some records (from page id 250) in our left_column div but only on page id 100 or a subpage of this page!

# First we define the content of the 'left_column' div:
left_column = COA
left_column {
   10 < lib.regularContent
   20 < lib.specialContent
}

# Display the lib.specialContent only on page id 100 or a subpage
[PIDinRootline = 100]
lib.specialContent = CONTENT
lib.specialContent {
   table = tt_content
   select {
      pidInList = 250
      orderBy = sorting
      languageField = sys_language_uid
   }
}
[end]

I could make a hundred examples but when you know to basics it isn’t that hard. If you want to know more about these conditions please read chapter 4 of the TSRef:
http://typo3.org/documentation/document-library/references/doc_core_tsref/4.1.0/view/4/1/

If you have any questions don’t hesitate to ask!

In this tutorial I’m assuming you already have a website. You also need 2 or more languages. In this case we have our default language (English) with two other languages (Dutch and German). If you do not have these languages you might want to make them first, else the tutorial won’t be correct. To check your languages go to the List module, click on the root (world-icon) of the TYPO3 installation and see if there are ‘Website Languages’. (See screenshot 1)

Screenshot 1. Click to enlarge!

Got your languages? Good! Now where can we find this wonderful module? The Localization Overview module can be found within the Info module.

1. Go to the Info module in the left main menu.
2. Select the rootpage of your website.
3. Select 'Localization Overview' from the top dropdown menu.

You’ll now see an overview of your pages with the default language pagetitles, and perhaps the pagetitle you already translated.

Screenshot 2. Click to enlarge!

As you can see in the screenshot column 3 and 4 are the Dutch and German pagetitles and still empty. To translate the default pages into a new language we now check all pages we want to translate and hit the ‘Create new translation headers’ button. This way we can translate all pages in 1 screen!

Screenshot 3. Click to enlarge!

The edit screen allows you to insert a new pagetitle for the (in this case Dutch) language. You can also hide the page of choose a different language you want to translate but these options aren’t relevant in this tutorial. Once you’ve inserted all your new pagetitles save the page.

Beware that your TYPO3 login expires by default after 1 hour!
This should be no problem with TYPO3 4.x but it doesn't hurt to
save regularly when inserting many new pagetitle! Better to save
3 times than ending up expired and start all over again...

Once your done and saved the page you’ll return to the Localization Overview page. I would recommend inserting 1 language at a time, this way you don’t need to keep switching languages in you head or make sure you enter the right language into the right field.

Screenshot 4. Click to enlarge!

I hope this tutorial was clear and helpful. If you have any questions don’t hesitate to ask.

Note: This is not an official preview but a trunk download from
the subversion repository. Features a subject to change!

Click to enlarge!

When installed, tt_news tells you to update to version 3.0 using a dedicated update screen. There seems to be no more option to disable the tabbed flexform interface, yet there are more options regarding the caching of newsitems.

Click to enlarge!

There are several database updates needed to be done. Each one can be easily applied using the update wizzard.

Click to enlarge!

With tt_news 3.0 comes a News Admin module! Within this module there are no unknown features yet, but it’s gives you a nice overview of your tt_news records. You can edit news items and categories from within the module.

Click to enlarge!

The updated flexform reveals some new changes: There are more options to display, and more alternative template parts. With the option dropdown box there is no posibility anymore to choose LIST and SINGLE within the same record. Also notice there is no selector for the starting point.

Click to enlarge!

There are a few more options than before. Image width and height are now in the flexform too.

Click to enlarge!

The startingpoint has moved from the first tab to the last tab…

Download  tt_news 3.0 and see for yourself:

WARNING: This extension is still under development and
should NOT be used in production environments!

Download tt_news 3.0 (Right-click save as, Trunk version 05-11-2009)