After installing the extension you will have to include it somehow in your TypoScript Setup. You will need a place where to put the contents of the extension (a marker in your HTML template).

Lets say you have defined a "DIV" with ID "leftcontent"

<div id="leftcontent">Left</div>

Then you assign the result of this extension to this marker. This is different wheter you use normal markers or the Template Auto Parser. I give examples for both:

With "normal" markers:

temp.mytemplate.marks.leftcontent < plugin.tx_kbcontslide_pi1

or with the Template Autoparser

temp.mytemplate.subparts.leftcontent < plugin.tx_kbcontslide_pi1

After this assignment you can take a look on your webpage (don't forget to clear the cache if you make changes) and you will notice that the content of the DIV "leftcontent" is already replaced by the content of the "Normal" column.

By default this extension displays the content of the "Normal" column. You can see how this default is achieved by looking at "EXT_DIR/ext_typoscript_setup.txt".

If you (most probably) want to change it to another column add the following TypoScript code to one of your templates. But be sure that the configuration of this extension is done before the plugin is assigned to a HTML marker.

plugin.tx_kbcontslide_pi1.content.select.where = colPos=1

If the plugin is configured this way it will display the contents of the "Left" column.

So the complete TypoScript setup for this extension will look like:

plugin.tx_kbcontslide_pi1.content.select.where = colPos=1

temp.mytemplate.subparts.leftcontent < plugin.tx_kbcontslide_pi1

It is also possible to modify the "plugin.tx_kbcontslide_pi1.content" further. You could for example define a more complex where statement. The extension uses standard Typo3 functions for generating the content so you could also overwrite the "content = CONTENT" definition from ext_typoscript_setup.txt with something completly different. But then the function of this plugin will most probably be userless (Pherhaps somebody finds some other use for this extension).

If you have more than one column which you would like to use with kb_cont_slide there is of course the possibility to do so. Instead of using the Content Slide TS object directly you have to assign it to your column first and then make all necessary settings. So the settings for each column don't overwrite each other.

To make a setup where 2 Columns are used by KB Content Slide you will need a TS setup similar to the followin:

lib.news < plugin.tx_kbcontslide_pi1

lib.news.content.select.where = colPos=2

lib.skurril < plugin.tx_kbcontslide_pi1

lib.skurril.content.select.where = colPos=4

Also you see that in this case I used “lib.” objects. As this setup was used on a TemplaVoila site. So Content Slide also works with Templa Voila !!!

The only difference to the previous examples is that the “where” is not set directly in plugin.tx_kbcontslide_pi1 but in a copied object.