t3lib_extMgm::addUserTSConfig(‘
page.RTE.config.your_table_name.field_name.showButtons = bold, italic, orderedlist, unorderedlist
‘);

In order to do this, we can follow any of the following methods:

METHOD 1:

1. Go to http://www.typo3.org/extensions then search for your extension, say tt_news
   
2. Just copy yhe download link of the t3x file, and now my link looked as below: http://typo3.org/fileadmin/ter/t/t/tt_news_3.0.1.t3x
   
3. We need the version 2.5.2, so change the version number of above URL to as follows:
   http://typo3.org/fileadmin/ter/t/t/tt_news_2.5.2.t3x
   

METHOD 2:

This is one way, the other way is when we use the update manager within TYPO3 BE, we get a drop down to select the version, and load it’s detail. Then we can install/update the necessary version. Sometimes the drop down may not have the needed version, so Method 1 may work in such cases!

METHOD3:

Most extensions were also under version control on typo3 forge, even here we can get the old files. We may however get some files/updates/changes that were not really published to the Extension Repository. So this may be slightly risky as well. Generally the first two methods are much more easier.

Easy:

1. go to BE
2. Click the Configuration module in left menu bar
3. Now use the drop down at the top, and select TYPO3_CONF_VARS.
4. Search for what you need
5. Click on the needed title
6. Now you get a array like this:
   $TYPO3_CONF_VARS['EXTCONF']['cachecleaner']['tables']['cache_pages']['expireField'] = ‘expires’;
   
7. Change this in your extension (in a PHP file) and include this file in ext_localconf.php
   OR Directly write inside ext_localconf.php (well this may not be very clean)

NOTE: The CONFIGURATION Module is like a TREE browser which lists all kind of available configurations available in TYPO3.
So we have endless chance to change and customize almost anything here!

NOTE2: The TYPO3 Configuration Module is also a place where you can see the current configuration that is in use.
This can be used for wide range of debugging, such as:

1. To analyze if a HOOK/XCLASS has been declared or not
2. To see if the configuration we specified has been really recognized by TYPO3

ENJOY!

GOAL: Add new field called company name, after the subheader field for tt_news of type “External URLS”

STEP 1: Look into the ext_tables.php containing the following method of adding new field to TCA Array.

t3lib_div::loadTCA(‘tt_news’);
t3lib_extMgm::addTCAcolumns(‘tt_news’,$tempColumns,1);
t3lib_extMgm::addToAllTCAtypes(‘tt_news’,'tx_ttnews_fieldcompany;;;;1-1-1′);

STEP 2: Replace the above 3 lines as follows:

t3lib_div::loadTCA(‘tt_news’);
t3lib_extMgm::addTCAcolumns(‘tt_news’,$tempColumns,1);
$TCA['tt_news']['types']['2']['showitem'] = str_replace(‘short,’, ‘short, tx_ttnews_fieldcompany,’, $TCA['tt_news']['types']['2']['showitem']);

STEP 2: Alternate, using TYPO3 API (Thanks to Oliver for the code):

t3lib_div::loadTCA(‘tt_news’);
t3lib_extMgm::addTCAcolumns(‘tt_news’,$tempColumns,1);
t3lib_extMgm::addToAllTCAtypes(“tt_news”,”tx_ttnews_fieldcompany;;;;1-1-1″, “”, “after:short”);

STEP 3 Clear cahce and check the news record.
That’s it, now clear your TYPO3 config cache, and check the record, the new field is now just after the sub header field in tt_news record of type External URL.

NOTE1:
You cannot use a hook if it is not already defined! So we can use XCLASS in such case.

NOTE2:
The steps defined here uses a tt_news hook as an example, however this method would generally work on all extensions that have a hook.

STEP 1: Check which hook to use.

I added some new fields, and I wanted them to be displayed in list/latest and single view templates of news.
I selected the “extraItemMarkerProcessor” hook that seemed to fit this need.

STEP 2: Check the inputs we get and add appropriate function inside out class

The hook in tt_news was defined as follows:

foreach($GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['tt_news']['extraItemMarkerHook'] as $_classRef) {

$_procObj = & t3lib_div::getUserObj($_classRef);
$markerArray = $_procObj->extraItemMarkerProcessor($markerArray, $row, $lConf, $this);

}

So all I did was to write a class with this method/function as follows:

class tx_ttnewshooks {

function extraItemMarkerProcessor($markerArray, $row, $lConf, $ttnews){
// MY CODE GOES HERE

return $markerArray;

}

}

STEP 3: Include our hook

It is now time to include our hook, so that tt_news knows that we would like to use this hook.
Here is what I did:

A. Use kickstarter to create your extension’s skeleton, let me call this as “ttnewshooks“.
ex: By adding information etc…
NOTE: Unfortunetely, I will not be covering how to create an extension with kickstarter.

B. Create a new file called ext_localconf.php (if it is not already here)

C. Add the following code inside this file:

<?php

if (!defined (“TYPO3_MODE”)) die (“Access denied.”);

if (TYPO3_MODE!=’BE’) {
require_once(t3lib_extMgm::extPath(‘ttnewshooks’).’class.ttnewshooks.php’);
}

$TYPO3_CONF_VARS['EXTCONF']['tt_news']['extraItemMarkerHook'][] = ‘tx_ttnewshooks’;

?>

STEP 4: Time to check if things work.
Generally there should not be any issues.
NOTE: Make sure that our new extension is installed, else this will never work!

Further Reference:
http://typo3.org/development/articles/how-to-use-existing-hooks/

Well, yes, still the basic stuff we need to find out is how to get this done.

Generally you might have seem in extensions that they use stdWrap, and consider you wish to process the content after the stdWrap is applied.

ex:
After generating a menu, after a news text is displayed from tt_news etc…

As with all my posts, I just love to keep thngs short, so I will just explain this with relation to a tt_news example:

Step 1: Find out where you can bind your user function:

I was in need of processing the news content to strip some special characters from word, so this is what I did.

I could also have used the plugin.tt_news.general_stdWrap.postUserFunc, I however did not wish to touch each field, as I only needed some selected fields to be affected.
Thus, on looking into tt_news/pi/class.tx_ttnews.php I found that there is a config I can make use of that is “itemMarkerArrayFunc”.

Step 2 : Write your user function.

NOTE 1:
Write your userFunc within standard PHP tags, and save it in fileadmin, or EXT folder.
ex:

<?php
//code here
?>

NOTE 2:
Makse sure to understand what type of data is available to us, well sometimes it might be an array as in this case.

NOTE 3:
Your function name should start with “user_”

NOTE 4:
Your function declaration should have enough arguments, if not you might be in a surprise.
Generally if you are using parseFunc of stdWrap your function may look like this:
ex:

function user_ProcessData($content,$config){

// do something with $content
$modifiedContent = $content . ” This is modifed”;
return $modifiedContent;

}

THE USER FUNCTION
In my case the function looks like this

function user_ProcessData($markerArray, $conf) {

$str = $markerArray['###NEWS_CONTENT###'];
$str = str_replace(‘###CUSTOMER###’,'Customer Name’,$str);
$markerArray['###NEWS_CONTENT###'] = $str ;
return $markerArray;

}

Step 3: Include this file in typo3
This can be done in several ways, and here is one such method:

# Add the following code to the setup section of your System Template record. ( we will usually have setup and constants here in General Tab )

includeLibs.itemMarkerArrayFunc = EXT:customext_libs/userNewsMarkerProcessFunc.php

# customext_libs – is the name of an extension

Step 4: Add final config, so that tt_news knows we want to make use of a parseFunc / userFunc

plugin.tt_news.itemMarkerArrayFunc = user_ProcessData

Step 5: This should generally work.
If not please make sure you followed everything as per the above seteps!

• Step 1: Set nothing for the libraryToUse contstant (of course in constants section)
  plugin.powermail.libraryToUse =
  
• Step 2: Set up a different template path for the formWrap — This is important, will explain later in Step3!
  To do this I will copy the formwrap.html located in typo3conf/ext/powermail/templates/tmpl_formwrap.html to fileadmin/templates and set following constant.
  plugin.powermail.template.formWrap = fileadmin/templates/tmpl_formwrap.html
  
  NOTE: You may change template even in setup section, check manual or ext_typoscript_setup.txt for details.
  
• Step 3: Remove the validation script from formwrap.html that we copied just now.
  If you look at the tempalte file, you can see folloing JavaScript:
  
  <script type=”text/javascript”>
  function formCallback(result, form) {
  window.status = “valiation callback for form ‘” + form.id + “‘: result = ” + result;
  }
  var valid = new Validation(‘###POWERMAIL_NAME###’, {immediate : true, onFormValidate : formCallback});
  </script>
  
  Remove the above completely including <script> tags.
  
• Step 4: Remove automatic inclusion of JS files using TypoScript. (IMPORTANT: This must appear in the setup section)
  page.includeJS.file31311 >
  page.headerData.31310 >
  

There you go, by now you should have disabled the output of all java scripts and inclusion of JS Libraries like mootools or prototype.
Now you are free to use any library you need.

NOTE: By now the default validation methods available in powermail are also disabled. Well we can easily use the jquery form validation!

This is probably caused because feeditadvanced did nt take into consideration the css files that are created by the js_css_optimizer.

Normally we do not need js_css_optimizer if we would like to edit content. So added a quick solution that disables the js_css_optimizer when using on feeditadvanced.

You will need to edit the following file:

typo3conf\ext\feeditadvanced\hooks\class.tx_feeditadvanced_pagerenderer.php

Open this and add the following 3 lines of code inside the IF Condition of the function preProcessPageRenderer():

unset($GLOBALS['TYPO3_CONF_VARS']['FE']['cssCompressHandler']);
unset($GLOBALS['TYPO3_CONF_VARS']['FE']['jsCompressHandler']);
unset($GLOBALS['TYPO3_CONF_VARS']['FE']['concatenateHandler']);

Full code for preProcessPageRenderer():

public function preProcessPageRenderer($params, $parentObject) {

if ($parentObject->getConcatenateFiles() && (t3lib_div::_GP(‘eID’) === ‘feeditadvanced’) && $GLOBALS['TBE_TEMPLATE']) {

unset($GLOBALS['TYPO3_CONF_VARS']['FE']['cssCompressHandler']);
unset($GLOBALS['TYPO3_CONF_VARS']['FE']['jsCompressHandler']);
unset($GLOBALS['TYPO3_CONF_VARS']['FE']['concatenateHandler']);

$compressor = t3lib_div::makeInstance(‘t3lib_compressor’);
$cssOptions = array(‘baseDirectories’ => $GLOBALS['TBE_TEMPLATE']->getSkinStylesheetDirectories());
$params['cssFiles'] = $compressor->concatenateCssFiles($params['cssFiles'], $cssOptions);
}
}

It would have been great if css files created by js_css_optimizer are used within feeditadvanced, unfortunately that is not the case at present.
Till then I hope we may use the above code.

So the moment I needed the services of feeditadvanced, I had to disable js_css_optimizer, so I added the following code:

unset($GLOBALS['TYPO3_CONF_VARS']['FE']['cssCompressHandler']);

We have to make sure that we do this at correct stage, for example, if the extension we wanted to disable has already finished it’s execution, then we may not get desired result, so we may have to add another hook that executes much before the hook we wanted to remove.

Generally we will need to edit tca.php and ext_tables.php.

To be more specific it involves adding two parameters.

1. Specify that you are using dividers to tabs “dividersstabs”
2. Mark all tabs using –div–

Let us see how.

1. Specify that you are using dividers to tabs “dividersstabs”

In the TCA array first look at the start of table definition. Generally this is located

EX:

$TCA['tx_myext_table] = array (
        'ctrl' => array (
                'title' => 'LLL:EXT:myext/locallang_db.xml:tx_myext_table,
                'label' => 'title',
                'tstamp' => 'tstamp',
                'crdate' => 'crdate',
                'cruser_id' => 'cruser_id',
                'languageField' => 'sys_language_uid',
                'transOrigPointerField' => 'l10n_parent',
                'transOrigDiffSourceField' => 'l10n_diffsource',
                'sortby' => 'sorting',
                'delete' => 'deleted',
                'dividers2tabs' => TRUE,
                'enablecolumns' => array (
                        'disabled' => 'hidden',
                ),
                'dynamicConfigFile' => t3lib_extMgm::extPath($_EXTKEY).'tca.php',
                'iconfile' => t3lib_extMgm::extRelPath($_EXTKEY).'icon_tx_myext_table.gif',
        ),
);

In the above config you can see that ‘dividers2tabs’ is set to TRUE

2. Mark all tabs using --div--

This is the step in which you would group all fields into different Tabs. This generally involves editing the TCA config usually locatd in tca.php.

In tca.php, look the section showitem, and add --div--;Tab Name,

EX:
'types' => array (
        '0' => array(
                'showitem' => '--div--;General,
                                sys_language_uid;;;;1-1-1, l10n_parent,
                                l10n_diffsource, hidden;;1,
                                --div--;Content,title;;;;3-3-3, parentid,top_page,content,
                                --div--;Header and Footer,footer,
                                background_image,background_align'
                )
),

As you can see I have added 3 tabs, General, Content, Header and Footer.

The idea is to add --div--; (two hypen followed by div and two hyphen and semicolon)

After semicolon add the “Title of your tab” and followed by a comma.

This section --div--;Tab Name, must be added just before a field, or after a field ends.

That should be it.

Happy coding.