After you set up a working tt_news (3.0.1)  :
Note : replace or declare the constants like $newsFolder for the corresponding values, page id’s and paths

Typoscript setup

plugin.tt_news {
 displayXML {
    rss2_tmplFile = {$tmplpath}tt_news_rss_2.tmpl
    xmlFormat = rss2
    xmlTitle = {$title} - latest news
    xmlLink = {$baseURL}newsarchive/
    xmlDesc = {$slogan}
    xmlLang = nl
    xmlIcon = fileadmin/templates/img/siteLogoRSS.gif
    title_stdWrap.htmlSpecialChars = 1
    title_stdWrap.htmlSpecialChars.preserveEntities = 1
    subheader_stdWrap.stripHtml = 1
    subheader_stdWrap.htmlSpecialChars = 1
    subheader_stdWrap.htmlSpecialChars.preserveEntities = 1
    subheader_stdWrap.crop = 300 | ... | 1
    subheader_stdWrap.ifEmpty.field = bodytext
    xmlLastBuildDate = 1
    xmlLimit = 10
    image.file.maxW = 180c

    # images in rss tmpl
    showImages = 1
 }
}

xmlnews = PAGE
xmlnews {
 typeNum = 100
 10 >
 10 < plugin.tt_news
 10.pid_list >
 10.pid_list = {$newsFolder}
 10.singlePid = {$newsArticle}
 10.defaultCode = XML

 #10.categoryMode = 1
 #10.categorySelection = 1  # would show only category 1

 config {
 disableAllHeaderCode = 1
 additionalHeaders = Content-type:text/xml
 no_cache = 1
 xhtml_cleaning = 0
 }
}

[globalVar = GP:type = 100]
 #URL prefix for images in feed
 config.absRefPrefix = {$baseURL}
 config.baseURL =
[global]

## RSS button in for example address bar in Firefox < version 4, what happened to RSS button in 4+ ?? :S
#page.headerData.12 = TEXT
#page.headerData.12.value = <link rel="alternate" type="application/rss+xml" title="{$title}: latest news" href="{$baseURL}newsarchive/rss.xml">

Template tt_news_rss_2.tmpl

It is assumed here you have the tt_news archive in /newsarchive  :

<!-- ###TEMPLATE_RSS2### begin -->###XML_DECLARATION###
<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>
 <!-- ###HEADER### begin -->
 <title>###SITE_TITLE###</title>
 <atom:link href="###SITE_LINK###newsarchive/rss.xml" rel="self" type="application/rss+xml" />
 <link>###SITE_LINK###</link>
 <description>###SITE_DESCRIPTION###</description>
 ###SITE_LANG###
 <image>
 <title>###SITE_TITLE###</title>
 <url>###IMG###</url>
 <link>###SITE_LINK###</link>
 <description>###SITE_DESCRIPTION###</description>
 </image>
 <generator>TYPO3 - get.content.right</generator>
 <docs>http://blogs.law.harvard.edu/tech/rss</docs>
 ###NEWS_COPYRIGHT###
 ###NEWS_WEBMASTER###
 ###NEWS_MANAGINGEDITOR###
 ###NEWS_LASTBUILD###
 <!-- ###HEADER### end -->
 <!-- ###CONTENT### begin -->
 <!-- ###NEWS### begin -->
 <item>
 <title>###NEWS_TITLE###</title>
 <link>###NEWS_LINK###</link>
 <description><![CDATA[###NEWS_SUBHEADER###]]>
 <![CDATA[<p></p>]]><![CDATA[###NEWS_IMAGE###]]>
 <![CDATA[###NEWS_CONTENT###]]></description>
 ###NEWS_CATEGORY###
 <guid>###NEWS_LINK###</guid>
 <pubDate>###NEWS_DATE###</pubDate>
 ###NEWS_RSS2_ENCLOSURES###
 </item>
 <!-- ###NEWS### end -->
 <!-- ###CONTENT### end -->
 </channel>
</rss><!-- ###TEMPLATE_RSS2### end -->

$tt_content_conf = array('tables' => 'tt_content'
      ,'source' => 33
      ,'dontCheckPid' => 1
      );
$extraRemark= $this->cObj->RECORDS($tt_content_conf);

The source number corresponds with the uid of the content element. You could also make a constant or a flexform value of this,  if you know how to build extensions you probably know how to do this.

Output :

Put a marker in the html-template of the extension. In my case this was ###EXTRAREMARK### in new_topic.html

Fill marker :

$marker = array(
    '###EXTRAREMARK###'            => $extraRemark,
etc... );

That’s all!

Powermail PHP field validation

At this moment jQuery is still not implemented in Powermail, though it seems they are working on it.  Unfortunately javascript cannot be switched of at the present (Powermail 1.5.3) via the constant editor. When using 2 different libraries chances are that for example jQuery or another lib might work ok and the field validation in Powermail will work fine with PHP. But.. the page contains errors and for example Internet Explorer will produce an annoying script error :

Powermail Javascript error in Internet Explorer

Disable javascript in Powermail

To get rid of this error and to get cleaner code you can do the following :

In Typoscript, setup disable the loading of the js :

page.includeJS.file31311 >
page.includeJS.file31312 >
page.includeJS.file31313 >
page.includeJS.file31314 >
page.headerData.31310 >

This will make sure prototype.js (or mootools.js), effects.js, fabtabulous.js and checkbox.js are not loaded in the HTML source. The last line makes sure the validation script is not loaded. More info on disabling the javascript in Powermail here.

Powermail javascript error in Internet Explorer

You might wanna think that this would solve it, however after that another error appears :

Another javascript error with Powermail

It seems in the source the following is the cause :

<script type="text/javascript">
  function formCallback(result, form) {
     window.status = "valiation callback for form '"
     + form.id + "': result = " + result;
   }
    var valid = new Validation('MyNiceForm',
    {immediate : true, onFormValidate : formCallback});
</script>

So we need to get rid of that too. This is located in the Powermail extension file “templates/tmpl_formwrap.html”. This file can be edited via the Extension Manager, choose Loaded extensions, than click on Powermail and Edit files. After removing the script part, save the file.

If you do see the message “SAVING IS DISABLED” instead of the save button go to the install manager first, find in all configuration “[noEdit]” (use ctrl-F in Firefox to search),  uncheck it and than scroll down totally and click on “Write to localconf.php”.

1. Changing the size of the TYPO3 RTE

Default size of the small RTE in TYPO3..

For the RTE this can easily be changed by editing the backenduser (via the List View under the globe level). There under options you can add your desired dimensions of the small version of the RTE :

options.RTESmallWidth = 800
options.RTESmallHeight = 600

Editing the backend user to get larger RTE

After this the RTE should look like :

Much more space to conveniently type some text

2. Changing the size of the TYPO3 Typoscript textarea windows

Not much space to code some TS in a relaxed way

This can be adjusted by going to the User Settings under the User Tools.

Changing the TYPO3 Typoscript textarea window size

There enable the following :

• Wide document background
• Make Textareas resizable
• Make Textareas flexible

Also you can put there the max height in pixels. After that the Typoscript windows are resizable by dragging in the lower right corner of the textareas. It should look like :

A larger and resizable TYPO3 Typoscript textarea window

]]> http://www.training-typo3.com/2010/05/20/enlarging-the-typoscript-and-rte-windows-in-the-typo3-backend/feed/ 0 http://www.training-typo3.com/2009/03/12/howto-enable-click-enlarge-images-in-the-rte/ http://www.training-typo3.com/2009/03/12/howto-enable-click-enlarge-images-in-the-rte/#comments Thu, 12 Mar 2009 11:06:37 +0000 Jacco Van der Post http://www.training-typo3.com/?p=151 Sometimes it’s handy to put images directly in the RTE instead of attaching them via the media tab in normal pagecontent or in a tt_news article. Together with a lightbox you can than browse through the images, which are spread in the text, like a gallery.

1.  Check “Enable images in the RTE” and “Enable click-enlarge on images” in htmlArea RTE

Via the extension manager click on the extension “htmlArea RTE” and there check “Enable images in the RTE” and “Enable click-enlarge on images”. After that click on Update on the bottom.

2. Include static template “Clickenlarge Rendering” (rtehtmlarea)

In your main typoscript template include the static template “Clickenlarge Rendering” (rtehtmlarea).

Include static Clickenlarge

3. Install and include “PMK Slimbox” and “PMK SlimBox for TT_news RTE-Text “  (optional)

If you like to use a Lightbox for nice image enlargement you could install PMK Slimbox and if you use tt_news you might want PMK SlimBox for TT_news RTE-Text, which allows  images inserted via the RTE also to have a lightbox. After installing via the extensionmanager include the static templates (see image above).

4. Check image button, tsconfig, default max width of RTE images

You should see now an image button in the RTE. If not, it is probably disabled in the tsconfig of the main page. For that edit the page properties of your root page and check under tab options. Make sure it is not listed under RTE.default.hidebuttons. If you would like to have a default width of images inserted in the RTE, you could enter there :

RTE.default.buttons.image.options.magic.maxWidth = 700

This gives the inserted image in the RTE maximum 700px width.

RTE insert image button

5. Insert image in RTE and set on click enlarge

After inserting the image, right click on it, choose “Image Properties” and check “Click-enlarge”

Set click enlarge

.

5. The MySQL database and UTF-8

Maybe you would like your database and TYPO3 to work with the UTF-8 characterset, which is advisable, escpecially with multi-language sites. Not all servers will automatically generate a UTF-8 database but rather create for example in latin1_swedish_ci. If you are not sure or if your host does not automatically let TYPO3 generate an UTF-8 database you could take the following steps :

5.1 Create the UTF-8 database with phpMyAdmin

Open phpMyAdmin (often installed by your host on your server), create a new database with collation utf8_general_ci

5.2 Edit localconf.php

Open typo3conf/localconf.php and add the following 2 lines :

$TYPO3_CONF_VARS['BE']['forceCharset'] = 'utf-8';
$TYPO3_CONF_VARS['SYS']['setDBinit'] = 'SET NAMES utf8;';

If you know the ImageMagick version, which is often version 6 on modern servers, this could also be a convenient moment to change the default version from 5 to 6 and accordingly also to change the dpi for a gifbuilder Freetype application to 96. You could do this later too in the installtool, so these are not really necessary now. Under “Basic configuration in the installtool” you can than look up the installed version on the server and set this version under “All configuration”. (ImageMagick is used to dynamically create or manipulate images, that’s why it’s advised in the TYPO3 server requirements to have it installed.)

$TYPO3_CONF_VARS['GFX']['im_version_5'] = 'im6';
$TYPO3_CONF_VARS['GFX']['TTFdpi'] = '96';

Last thing you may want to set if you run your website on a shared hosting and do not want to hold to many connections – which can result in your site and other sites going offline (“The current username, password or host was not accepted when the connection to the database was attempted to be established! database error”.  )  :

$TYPO3_CONF_VARS['SYS']['no_pconnect'] = '1';

6. The TYPO3 installtool

6.1 TYPO3 installtool step 1

After having chmodded the files and folders it is time to launch the installtool. Direct your browser to your new site, e.g. www.training-typo3.com and the install tool should appear, without errors if the guidelines in part 1 are followed. Fill in the mySQL database username, password and host (= often localhost).

TYPO3 install tool, step 2

6.2 TYPO3 installtool step 2

Depending on your server / host you can either create a new database or choose an pre-created empty database, which for example has been made with phpMyAdmin. If you rather or need to create a database with phpMyAdmin or another tool, you might want the collation to be utf8_general_ci or utf8_unicode_ci. If you let TYPO3 create a database, verify later in for example phpMyAdmin that the database and the tables are UTF-8.

6.3 TYPO3 installtool step 3, Go!

Simply click on “Import database” and … you’re done!

Click on “Continue to configure TYPO3″, there enter a new password for the installtool. After updating, choose “Basic configuration” from the top menu.

6.4 TYPO3 installtool basic configuration

TYPO3 install tool basic configuration

Make sure that everything there is checked ok. If not, read for example part 1 of this tutorial and fix the requirements, chmods etc. Try send a test mail if you like (don’t worry about the warning “sendmail program not found or not executable”,  if it works it works.). If you for example need to enter a path there for the ImageMagick installation do it and scroll totally downwards to update localconf.php. This file is pretty important with some global configuration, and is located on your server in the folder typo3conf. If you once run into trouble by for example mixing the wrong extensions and you can’t get properly in to the backend you can in that file delete some extensions from being installed.

After “Basic Configuration” you could check “Image Processing” and run some cool tests there to check wether ImageMagick, GDlib and Freetype work ok. Perhaps you get a warning you need to set [GFX][im_version_5] on im6 in “All Configuration”, depending on which version of ImageMagick you use.

After this the initial setup is done and it’s time to login on the backend!

7. The backend

Login the backend like www.yoursite.com/typo3 , after install the username is “admin” and the password is “password”. When in the backend you will get some notices in a yellow window. Follow the instructions to get rid of the warnings.

————

Soon part 3 of this tutorial with videos including an explanation of how to parse content from the backend on the frontend, where to learn more about typoscript, making a HTML template and using TemplaVoila!

1. Install Static info tables

Download and install the extension static info tables in the extensionmanager. This adds some database info in TYPO3 with countries, languages, currencies etc. After installing, include static in your main typoscript template (see image under 8. Realurl and multilanguage). If you do not install this extension, the localisation tab in TemplaVoila will not appear.

Installing this extension takes a lot of time so if your PHP.ini has limited the maximum execution time on 30 seconds, you might get an error while installing. If you get this error you can try to add in the TYPO3 .htaccess file the line php_value max_execution_time 90 or higher. If this does not work contact your webhost.

2. Create website languages

Go via List and click on the image of the “globe” level, that is the very top of the page tree. (NOTE: this has changed in newer TYPO3 versions. The highest level has now a TYPO3 logo.) There create the wanted languages. Fill in language, iso code and flag. We use english as default in this example, no need to define that one. Pay attention to the id’s of the languages which you can see if you hover with the mouse over the symbol. Those id’s need to be used later in realurl.

3. Check if langdisable is in TemplaVoila data source

This code is normally in the datastructure of a templavoila template :

    <meta>
        <langDisable>1</langDisable>
    </meta>

You can verify that in the DS record of the templavoila template.

4. Define the languages in typoscript.

In the setup of the main typoscript template the following code has been put. In our example our default language is enlish and we included spanish, german, dutch, french and portuguese. The id’s have to be identic to the created weblanguages. The default language has uid 0.

config.linkVars = L
config.uniqueLinkVars = 1
config.sys_language_overlay = content_fallback
config.language = en
config.locale_all = en_EN
config.htmlTag_langKey = en-EN
config.sys_language_uid = 0
[browser = msie]
config.htmlTag_setParams = xmlns="http://www.w3.org/1999/xhtml" xmlns:v=”urn:schemas-microsoft-com:vml” xml:lang="en"

[globalVar = GP:L = 2]
config.language = es
config.locale_all = es_ES
config.htmlTag_langKey = es-ES
config.sys_language_uid = 2
[globalVar = GP:L = 2] && [browser = msie]
config.htmlTag_setParams = xmlns="http://www.w3.org/1999/xhtml" xmlns:v=”urn:schemas-microsoft-com:vml” xml:lang="es"

[globalVar = GP:L = 3]
config.language = de
config.locale_all = de_DE
config.htmlTag_langKey = de-DE
config.sys_language_uid = 3
[globalVar = GP:L = 3] && [browser = msie]
config.htmlTag_setParams = xmlns="http://www.w3.org/1999/xhtml" xmlns:v=”urn:schemas-microsoft-com:vml” xml:lang="de"

[globalVar = GP:L = 4]
config.language = nl
config.locale_all = nl_NL
config.htmlTag_langKey = nl-NL
config.sys_language_uid = 4
[globalVar = GP:L = 4] && [browser = msie]
config.htmlTag_setParams = xmlns="http://www.w3.org/1999/xhtml" xmlns:v=”urn:schemas-microsoft-com:vml” xml:lang="nl"

[globalVar = GP:L = 5]
config.language = fr
config.sys_language_uid = 5
config.locale_all = fr_FR
config.htmlTag_langKey = fr-FR
[globalVar = GP:L = 5] && [browser = msie]
config.htmlTag_setParams = xmlns="http://www.w3.org/1999/xhtml" xmlns:v=”urn:schemas-microsoft-com:vml” xml:lang="fr"

[globalVar = GP:L = 6]
config.language = pt
config.locale_all = pt_PT
config.htmlTag_langKey = pt-PT
config.sys_language_uid = 6
[globalVar = GP:L = 6] && [browser = msie]
config.htmlTag_setParams = xmlns="http://www.w3.org/1999/xhtml" xmlns:v=”urn:schemas-microsoft-com:vml” xml:lang="pt"
[global]

For exact explaination what this code does read the article Creating multilanguage sites with TemplaVoila or the Frontend Localization Guide. You can read here more about XHTML and language in TYPO3.

For now just copy it and adjust to your languages. Make sure you end with [global]. Without realurl installed your urls will now be something like www.yourwebsite.com/index.php?id=1&L=2 , where L=2 means that you get the Spanish version of the page.

5. Put the default language and flag in TSconfig

On your root page edit the page properties. Under Options include in TSConfig :

mod.SHARED.defaultLanguageLabel = English
mod.SHARED.defaultLanguageFlag = gb.gif

This sets the default language on english and uses the english flag in the backend.

6. Create new page translation and pagecontent

Click via Page on the page where you wish to create a new translation. There choose the localization view tab and create a new page translation.

After that you can fill in the pagetitle for that language.

When you create new pagecontent you now should be able to choose the language for that page.

7. Creating a language selector on the TYPO3 website

For the language selector I installed in the extension manager the extension sr_language_menu. No configuration is needed if your default language is english. If not change in constant editor the default language and country. For example for dutch :

plugin.tx_srlanguagemenu_pi1.defaultLanguageISOCode = NL
plugin.tx_srlanguagemenu_pi1.defaultCountryISOCode = NL

You can add this extension as as plugin on your pages via pagecontent or you could map it with TemplaVoila. I prefer to map it so it appears on each page. To do that create a sysfolder, call it elements or something. In the sysfolder create pagecontent and choose Language Selection. There you need to select the languages from the globe level and choose if you want a dropdown list or flags. Note that you do not need to add the default language here (english in this example).

In the TemplaVoila html template add for example

<div id="language-selector"><!-- languages --></div>

Go via List to the TemplaVoila storage folder, click on the TO icon before your template and than templavoila, modify DS/TO. Add a new data element language. Choose as mapping type Element and as Editing Type “typoscript object path”, fill in after update lib.language.

Update, click on map, choose as Mapping Window “mode: html source” and click on the the new created div. Than click SET and “save as” to overwrite the TemplaVoila template. Since this is not a TemplaVoila tutorial I do not go further into this, however these are pretty much the steps needed, so should be sufficient.

Now, in your typoscript template add the following under setup:

lib.language = RECORDS
lib.language.tables = tt_content
lib.language.source = 62

The number needs to correspond with the id of the pagecontent element. You can see the id by hovering with the mouse over the icon before the Language menu item under the folder elements as stated above.

When you’re set and done clear all cache.

If you now check on the frontend of your site the language selector should be visible and working. Note that on a certain page only the languages will appear in the selector for which you made a page translation.

Only thing to do now is putting it on the right place in the design by adding something like this in your CSS :

#language-selector {
      left: 500px;
      top:100px;
      position:absolute;
      z-index:10;
     }

8. Realurl and multilanguage

If you want nice url’s you may want to install the extension Realurl. After installing uncheck “Enable automatic configuration” in the extension manager at the realurl extension. In the main typoscript template the following code needs to be put under setup :

    tx_realurl_enable = 1
    baseURL = http://www.yourwebsite.com/
    simulateStaticDocuments = 0
    prefixLocalAnchors = all

Read here about the needed .htaccess file at the root of TYPO3 folder. This is absolute necessary.

Since I am lazy I use the nice pre configuration of the extension CB Realurl (cbrealurl). It includes configuration for some popular extensions like tt_news. (Else you need to create manually a realurl configuration and include it in the file localconf.php.)
Install cbrealurl in the extension manager and include static in your main typoscript template.

Now you need to alter the file realurl.php in the extension cbrealurl with your languages. Unfortunately this needs to be done in php instead of for example via the constant editor.

Click on the extension manager, click on “Cannonbose RealURL Configuration Helper” then choose edit files.

You see there the languages defined when you scroll down a little. Default are some other languages defined than you see in the image above.  In this example our default language is english and we included spanish, german, dutch, french and portuguese. The id’s have to be identic to the created web languages – explained under point 2.

In the url you now will get http://www.yourdomain.com/pageblabla/ for english and for the other languages it will become http://www.yourdomain.com/es/pageblabla/ ,  http://www.yourdomain.com/de/pageblabla/ etc.

If you do see the message “SAVING IS DISABLED” instead of the save button go to the install manager first, find in all configuration “[noEdit]” (use ctrl-F in Firefox to search),  uncheck it and than scroll down totally and click on “Write to localconf.php”.

I know it’s not a nice way to edit in the extensionmanager, however its quick and dirty. (You could also create a custom file where you overwrite the default configuration, since on line 664 of realurl.php it states $customFile   = ‘../../realurl-custom.php’; ).

Notes

• Note that on TYPO3 versions 4.2.2 and 4.2.3 there are problems at the moment of this writing with realurl and multilanguage. Description of the bug ” Wrong path for links to other language versions ” is found on the bugtracker.  On 4.2.1 and lower there are no problems. In the examples realurl 1.5.2 and cbrealurl 1.1.0 were used on TYPO3 4.2.1.
  Update 12/1/09 : it seems this problem is fixed in the core of TYPO3 4.2.4
  
• This tutorial is partly based on the article Creating multilanguage sites with TemplaVoila by Dmitry Dulepov.

1. First of all I downloaded and installed these extensions. Mind the order!

• dam_1.0.14.t3x
• typoscripttools_0.0.2.t3x (this extension is special for T3Blog)
• sfpantispam_0.0.0.t3x
• t3blog_0.5.0.t3x

2. After installing I made a new page in my new and still empty site : Blog and created a new template there. In the template include the static templates as shown in the order as shown here.

3. I went to the constant editor (via Template of the Web menu, click on the new Blog page.) There fill in at least the baseurl and the id of the new blog page. Save and clear cache.

Then the blog worked! After that I added an extra CSS to style the blog a bit in an own way.

The default template delivered with it can be found in static/t3blog/template/setup.txt. So I copied a part of it to change it in the setup of the TS template I created in the blog page. For example I changed the right column to the left and disabled the right column. Also I disabled some widgets like the RSS which I didnt get to work yet.

#typoscript setup code

plugin.tx_t3blog_pi1.layoutBlog.20 >

plugin.tx_t3blog_pi1.layoutBlog.40 >

plugin.tx_t3blog_pi1.layoutBlog {

    #right Content

    40 = COA

    40 {

        stdWrap {

            wrap = <div id="col3">|</div>

            required = 1

        }

            10 = TEXT

        10 {

            value = <!-- -->

        }

    }

    #left Content

    20 = COA

    20 {

        stdWrap {

            wrap = <div id="col1">|</div>

            required = 1

        }

        5 = TEXT

        5 {

            field = searchBox

        }

        10 = TEXT

        10 {

            field = feed

        }

        #20 = TEXT

        #20 {

        #    field = calendar

        #}

        30 = TEXT

        30 {

            field = latestPostNav

        }

        40 = TEXT

        40 {

            field = categories

        }

        50 = TEXT

        50 {

            field = blogrollList

        }

        60 = TEXT

        60 {

            field = latestCommentsNav

        }

        70 = TEXT

        70 {

            field = archive

        }

        #80 = TEXT

        #80 {

        #    field = rss

        #}

        #90 = TEXT

        #90 {

        #    field = socialBookmarks

        #}

    }

    #footer

}

The RSS is strange that it does not work, since I filled in the needed TS which are explained in the manual.

The html and CSS of the blog and the widgets are not valid and thus contain of some errors which I suppose can be fixed if you dive in the extensions code. In internet Explorer there is a small error about an unvalid character.

The RTE sometimes just disappeared when I tried to create a 2nd pagecontent block in a single post.

Unfortunately the other pages of the site will not work out of the box with the template of the blog so I had to create quickly a Templavoila template to have pages like contact on the trial site. Since the template which comes with the blog uses it’s own CSS I created a blog.css which only gets loaded for the blogpage and this overwrites some CSS of the extension.

Later I tried to create a blog page myself by using a Templavoila page and just put some widgets from the blog extension by putting plugins on the page. This worked good. However in the list view of the posts the links in the post itself dissapeared..

Verdict : I feel the extension is still not mature enough and full of little bugs which annoyed me so much I decided to go ahead with WordPress for now. However it is a nice start to allow TYPO3 to have a good out of the box blog system instead of installing and combining extensions like tt_news, comments, tagcloud, calendar etc. For this site I am to lazy and just use WordPress for blogging   But I am looking forward to a bugfix release of T3Blog!

1. Check server requirements and download TYPO3

When you install TYPO3 the first time you need to download from TYPO3.org the “source with dummy site.zip”. Make sure your server meets the requirements of TYPO3. In general you will want at least a Linux Apache server with PHP 5.2, mySQL and Imagemagick.

2. Upload TYPO3 to your webserver

Extract it and upload it to your webserver with a reliable FTP client like for example Filezilla.

3. Put the right .htaccess in place

This is also a good time to immediately include the .htaccess. In the .htaccess you need to put in some rules for Realurl or Cooluri. Those are 2 extensions which allow to create nice urls. Instead of having http://www.typo3-course.com/index.php?id=3 we and for example Google prefer http://www.typo3-course.com/blog.html

To be able to get this, make sure your server has the Apache module modrewrite. So do not use a host which runs a Windows webserver! Unless you’re very handy cuz peeps seem to get RealUrl running on Windows. Google.

Also in the .htaccess there can be put some rules for PHP which depending on the server allows to override some fixed settings in PHP.ini. TYPO3 needs at least 32 mb PHP memory. The post_max_size sometimes needs to be set if you getting in troubles while installing a larger extension. The upload_max_filesize you may want to adjust if you like to be able to upload larger files in the backend, for example video. You can learn here more about allowing uploading large files in TYPO3.

In general this is the .htaccess you want in the root (so next to index.php) of the TYPO3 installation :

php_value memory_limit 128M

#Maximum size of POST data that PHP will accept. Not required.
php_value post_max_size 64M

#Maximum allowed size for uploaded files. Not required.
php_value upload_max_filesize 64M

RewriteEngine On
RewriteRule ^typo3$ - [L]
RewriteRule ^typo3/.*$ - [L]

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-l
RewriteRule .* index.php

Since you are not allowed to rename a file to .htaccess in Windows or OSX, create a new file with your favourite text (Windows) editor / Apple paste the code from above in it and save it as .htaccess. You can throw away the file _.htaccess which is included in the TYPO3 package.

4. Chmod folders and file

After copying via the FTP client of all the files and the .htaccess you now need to chmod some folders and 1 file with the FTP client. Just right click on the folders within for example Filezilla and choose CHMOD and set the following on 777. Sometimes 755 is also enough and sometimes you do not need to chmod at all. This depends on your webhost. If you get a message while running the install wizard that the folder is not writeable you need 777 instead of 755. The folders / file :

• typo3temp
• typo3conf
• typo3conf/localconf.php
• typo3conf/ext
• typo3conf/l10n
• typo3/ext
• uploads
• uploads/pics
• uploads/media
• uploads/tf
• fileadmin
• fileadmin/_temp_
• fileadmin/user_upload

After that it is time to run www.yourdomain.com to start the install wizard. Soon part 2 of this simple installation guide.