lib.customMenu = HMENU
lib.customMenu {
 1 = TMENU
 1  {
        wrap = |

        NO.allWrap = |
        NO.stdWrap.htmlSpecialChars = 1
        NO.after.cObject = COA
        NO.after.cObject {
            20 = CASE
            20 {
               key.field = uid
               default = RECORDS
               default.tables = tt_content
               default.conf.tt_content < tt_content
               default.conf.tt_content.stdWrap.innerWrap >               

               14 < .default
               14.source = {$submenu_element_14}

               15 < .default
               15.source = {$submenu_element_15}

               16 < .default
               16.source = {$submenu_element_16}

               17 < .default
               17.source = {$submenu_element_17}

            }            

        }
        ACT = 1
        ACT.after.cObject < .NO.after.cObject
        ACT.allWrap = |
        ACT.ATagParams = class="act"
        ACT.stdWrap.htmlSpecialChars = 1

        CUR < .ACT
        CUR.ATagParams = class="cur"
    }
}

This code cannot be used as it is, you will need to make sure the DHTML/JavaScript code for the sub menu items are configured accordingly.

Further References:

1. [TYPO3-english] conditional menu based on menu page-id
   http://lists.typo3.org/pipermail/typo3-english/2009-November/065557.html
2. [TYPO3-english] Custom class in tmenu according to uid page
   http://lists.typo3.org/pipermail/typo3-english/2010-February/067336.html

10 = IMAGE
10 {
    file.import {
         cObject = COA
         cObject {
             10 = TEXT
              10.data = field:image_path
             20 = TEXT
             20.data = field:image_name
         }
    }
}

Hope this helps.

METHOD 1:

temp.pTitle = HMENU
temp.pTitle {
special = list
special.value = {$my_page_uid}
1 = TMENU
1 {
NO {
doNotLinkIt = 1
}
}
}

METHOD 2: (The localization may not work fine in the below method)

lib.pagetitle = RECORDS
lib.pagetitle {
source.data = page:uid
tables = pages
conf.pages = TEXT
conf.pages.field = nav_title
}

Getting Current Page Title:

lib.pagetitle = TEXT
lib.pagetitle.field=title

Page title of parent page:

lib.pagetitle = TEXT
lib.pagetitle.data = leveltitle:-2
OR
lib.pagetitle = TEXT
lib.pagetitle.data = leveltitle:-3

Inserting page title within a HMENU

temp_pagetitle = TEXT
temp_pagetitle.data = leveltitle:-2

leftMenu = HMENU
leftMenu.stdWrap.preCObject < temp.leftmenu_pagetitle
leftMenu.1 = TMENU
leftMenu.1.wrap = <ul class=”cw_leftmenu”>|</ul>
leftMenu.1.NO.wrapItemAndSub = <li>|</li>
leftMenu.1.ACT = 1
leftMenu.1.ACT.wrapItemAndSub = <li>|</li>
leftMenu.1.ACT.allWrap = <span class=”active_menu”>|</span>
leftMenu.1.CUR = 1
leftMenu.1.CUR.allWrap = <span class=”cur_menu”>|</span>
leftMenu.2 < .1
leftMenu.3 < .2

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!

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

• 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!

RTE.default.proc.dontConvBRtoParagraph = 1

That’s it.

As the code describes it does not allow BR to convert to Paragraph.

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

3) Insert the image in RTE and set on “Click-enlarge” option.

The issue is reproduceable even on Typo3 4.2.8, I am not sure if this is fixed on 4.3 onwards.

There is a patch that we can use to patch felogin as given on the following URL:
http://bugs.typo3.org/view.php?id=8677

Due to various reasons it may not always be possible to patch.
In such circumstances it is wiser to use an alternate technique, such as creating the Logout link manually.
One such example is:

[loginUser = *]  

lib.logoutbox = COA
lib.logoutbox {
    20 = TEXT
    20 {
       data = TSFE:fe_user|user|username
       # link to account edit page
       stdWrap.typolink.parameter = 60
    }
    30 = IMAGE
    30 {
        file = fileadmin/templates/images/logout.gif
        stdWrap {

             # Let us link to home page for logging out
             typolink.parameter = 1
             typolink.additionalParams = &logintype=logout
             wrap =  |
         }
    }
}

[end]

In this example I am displaying the logged in username (which links to user account page) followed by a working logout button.

Note:
- Here we are not using the felogin plugin.
- Do not link the logout button to any access restricted page.

The following page from Typo3wizard might be useful for displaying more user-details if needed:
http://www.typo3wizard.com/en/snippets/cool-stuff-typoscript/userinfo-for-currently-logged-in-user.html

config {
prefixLocalAnchors = all
}

This  replaces  all links like <a href=”#” > into <a href=”[url]#”>