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

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.

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!

1. Make sure you are logged in to the BE of same domain.

In a multi-domain setup, if you are logged in www.domain-a.com, and you try to view www.domain-b, then don’t expect the preview / admin panel to work.
This simply does not work!

2. user and/or group setup:

admPanel=1
admPanel {
enable.edit = 1
enable.edit.hide=1
enable.preview = 1
enable.cache = 0
enable.info = 1
module.edit.forceDisplayFieldIcons = 1
module.edit.forceDisplayIcons = 1
module.edit.forceNoPopup = 0
hide = 0
}

3. root template setup:

config.admPanel=1

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.

http://typo3.org/documentation/document-library/references/doc_core_tsref/current/

Check the article “1.12. PHP include scripts” and 1.13. Case story for detailed info.

In short we can easily include a script in two ways.

Both these code must be written in the setup section of a template record.

1. Using the CONFIG object.
   ex:
   config.includeLibrary = fileadmin/templates/myscript.php
2. Using the PAGE object.
   ex:
   page.100.file = fileadmin/templates/myscript.php

That should do the trick. Fo more info I suggest that you please refer “doc_core_tsref“.

There exists a documetnation about the same titled “Declaring constants for the Constant editor” which can be easily located in the typo3 core documentation titled “TypoScript Syntax and In-depth Study – doc_core_ts”.

1. You are unable to see the color picker, that means you need to add it to the list of available buttons.
   This can be done by adding “textcolor” to the list of existing buttons in showButtons property.
   ex:
   RTE.default.showButtons = ………….. textstyle, bold, italic, textcolor
   (NOTE: The order here is not important)
   
2. You should also remove the “textcolor” from the list of buttons in the hideButtons property. i.e. from RTE.default.showButtons =
   
3. Place the “textcolor” button in a suitable place of your preference using the toolbarOrder property.
   ex:
   RTE.default.toolbarOrder = …. space, textstyle, textcolor, …etc….
   
4. Check if color picker is enabled or not, by making sure that “disableColorPicker” is set to 0
   ex:
   RTE.default.disableColorPicker = 0
   
5. RTE might use the font tag to set colors, we can make sure that this does not happen by addin the font tag to the list of tags to be removed.
   ex:
   RTE.default.removeTags = font
   
6. After following step 5, the font tags are no longer used for specifying font colors, hence we should make sure to set the useCSS property to true, otherwise the colors would not appear on the front-end, nor they are saved.
   ex:
   RTE.default.useCSS = 1
   (NOTE: If you wish to use font tags for text coloring thisfeature need not be set)
   
   Hope these steps would be helpful to you!

Additional Notes:
The above steps are sometimes just not enough and you also need to make sure that the property “[allowStyleAttribute]” is enabled in the rtehtmlarea Extension’s configuration as shown in the screenshot.

An issue Related Typo3 Update:

• When typo3 is upgraded from 4.2 to 4.3 no matter what we do, colorpicker just does not get displayed.
  To solve this you will need to remove the rtehtmlarea config array in the localconf.php manually!
  - Just delete the line $TYPO3_CONF_VARS['EXT']['extConf']['rtehtmlarea'] = ……etc….
  - Go to rtehtmlarea configuration in Extension manager and click “Update” to save the new config.
  This should now make the textcolor to appear again.

Consider you have selected a specific Templavoila Template and you wish to have a different type of menu based on the selected template.
In such case it would be easy to change menu styles if the entire menu is enclosed in a separate CSS class.

I have given an example where I am checking for template IDs 10 , 11. If this template is used for current page I am changing it’s class.

lib.mymenu = HMENU
lib.mymenu {
entryLevel = 1
stdWrap.ifEmpty.wrap = &nbsp;

1 = TMENU
1 {
wrap = <ul>|</ul>
NO.wrapItemAndSub = |</li>
NO.allWrap = <li>|
NO.allWrap {
override = <li class=”alternate_menu”>|
override.if.value = 10,11
override.if.isInList.field = tx_templavoila_to
}
# same way we can configure ACT and CUR as well
ACT = 1
CUR = 1

}

# For second level I would like to change the class of the A Tag
2 < .1
2.wrap = <ul>|</ul>
2.CUR.ATagParams = id=”cur_menu”
2.ACT.ATagParams.cObject = TEXT
2.ACT.ATagParams.cObject {
override = class=”cur_menu_a”
override.if.value = 10,11
override.if.isInList.field = tx_templavoila_to
}
3 < .2

#let us generate the 3rd level only if the page uses the Template of our choice.
3.if {
value = 10,11
isInList.field = tx_templavoila_to
}

}

Not all templates may have a template ID specified, in such case we need to use the sliding feature.
When we use the sliding feature the template id of parent ID is used.
We can do this Like:

isInList.data = levelfield:-1, tx_templavoila_to, slide

Note:
Usually Templates are stored in the Storage Folder, and you can view the Template IDs of Templavoila Template Objects from the list view!