[blog...]

Quite often I want to set a link to an article I wrote somewhere else on this TYPO3 page. This is no problem, if this article is on a separate page with a unique ID.

But howto set a link to a t3blog article or a tt_news article?

As usual, there are several possibilities:

• add the AOE Linkhandler extension
• add the RTE Generic Record extension
• replace your htmlarea RTE with tinymce_rte with buildin linkhander support

I tried them all. To link a tt_news article is no problem with all of it. But howto link a t3blog-article? This seems to be not so easy if you're using realurl!

[...]

By adding the following Typoscript to your page TSconfig (Page->Edit->Options), tinymce_rte shows you the articles and t3blog-categories when selecting the blog-record folder (in my case ID is 3):

RTE.default {  
     linkhandler {       
       tx_t3blog_post {          
           default { 
              # instead of default you could write the id of the storage folder             
              # id of the Single News Page             
              parameter = 3             
              additionalParams = &tx_t3blog_pi1[blogList][showUidPerma]={field:uid}
              additionalParams.insertData = 1
              select = uid,title as header,hidden
              sorting = crdate desc
           }
       }        

       tx_t3blog_cat {            
           default {                
              parameter = 3                
              additionalParams = &tx_t3blog_pi1[blogList][category]={field:uid}                
              additionalParams.insertData = 1                
              select = uid,catname as header,hidden                
              sorting = crdate desc            
           }
       } 
    }
 }

Unfortunately it is not possible to select the tags from the menu. This is because all tags of one post are stored in the tagClouds field of the tx_t3blog_post table. So still have to add an external link to your page and add e.g. "blog/tags/typo3" if you're using realurl, your blog is located on page "blog" and you want to select the "typo3" tag.

Quite often you have the requirement to list events, news, references or whatever in a cronological order on your webpage. The tt_news extension of Typo3 is capable to do a lot of things. Though it is quite complex to configure it to your needs.

One missing feature is a calendar view of the upcoming events. With newscalendar you can do this.

As of version 1.10 newscalendar uses the jQuery tools from flowplayer.org. In my (news-) template I configured my own css for calendar and context menu and I modified the default images of the tooltip background (live demo on doris.bigga.de/vortraege/):

plugin.tx_newscalendar_pi1.calendar.startWeekDay = 1
plugin.tx_newscalendar_pi1.file.cssContextMenu = fileadmin/templates/doris/css/cssContextMenu.css
plugin.tx_newscalendar_pi1.file.cssCalendar = fileadmin/templates/doris/css/cssCalendar.css
plugin.tx_newscalendar_pi1.file.jsJQueryTooltip = fileadmin/templates/doris/js/jquery.tools.min.js

In the last statement I include my own version of the jquery tools. I just changed the statement "relative:false" into "relative:true". Otherwise the tooltip isn't shown above the date but somewhere because the javascript misscalculates the position.

I added a bugreport to the typo3 forge bugtracker: http://forge.typo3.org/issues/show/5313

UPDATE (2009-11-26):

There seems to be a lot of development in progress. Today version 2.1.1 is online and my bug is fixed because the jQuerytooltip has been dropped. So I disabled the two lines in the template again:

# plugin.tx_newscalendar_pi1.file.cssContextMenu = fileadmin/templates/doris/css/cssContextMenu.css

# plugin.tx_newscalendar_pi1.file.jsJQueryTooltip = fileadmin/templates/doris/js/jquery.tools.min.js

Now I can modify the default scheme by (e.g.):

plugin.tx_newscalendar_pi1.tip.backgroundColor=#E3EECB

plugin.tx_newscalendar_pi1.tip.borderWidth=2

plugin.tx_newscalendar_pi1.tip.positions='top'

UPDATE (2010-02-03):

Today version 2.1.4 is online. Fixing errors which has already been fixed and got lost in 2.1.2. Confusing.