Tag Archives: backend

tt_news and the t3lib_SpriteManager

Posted on by
Reply

as of TYPO3 4.4 the SpriteManager appeared, tt_news (3.0.1) starts creating lines in the deprecated log. it´s one line changed in tt_news´ ext_tables.php file.

$ICON_TYPES['news'] = array('icon' => t3lib_extMgm::extRelPath($_EXTKEY).'res/gfx/ext_icon_ttnews_folder.gif');

must be changed to:

t3lib_SpriteManager::addTcaTypeIcon('pages', 'contains-news', '../typo3conf/ext/tt_news/res/gfx/ext_icon_ttnews_folder.gif');

this is obviously part of the deprecation message thus a no-brainer. but this way you can avoid even the first appearance of this message o.O

replyto with the standard mailform ce in TYPO3

Posted on by
Reply

if you want the standard mailform content element in TYPO3 to send emails not from the ugly www-data@server.com sender but the writer´s email adress and name you just need to use explicitly labelled fields as follows:

  • from_name
  • from_email

This will do the trick. But there´s even more. If you need to provide a reply-to attribute you can do this by using these fields (which may be hidden):

  • replyto_name
  • replyto_from

Well, nowadays i´d recommend sophisticated mail form extensions like powermail but if you happen to edit a project that might help :)

tooltips with ext:contagged

Posted on by
1

for some reason the very good extension contagged does not provide the dropdown to select what type of term the current item is. so all my entries in the sysfolder “terms” have type 0.

the little tweak in the userTS changes all newly created terms to be a tooltip:

TCAdefaults.tx_contagged_terms.term_type = tooltip

a small UPDATE in mysql made the already existing terms to tooltips as well. a post before i saved how to have only contagged items in this sysfolder.

to avoid editor´s overkill when just creating a little tooltip i also remove some fields from the very flexible contagged terms item in PageTS:


TCEFORM.tx_contagged_terms {
 image.disabled = 1
 imagecaption.disabled = 1
 imagetitle.disabled = 1
 imagealt.disabled = 1
 exclude.disabled = 1
 term_type.disabled = 1
 term_replace.disabled = 1
 desc_short.disabled = 1
 starttime.disabled = 1
 endtime.disabled = 1
 fe_group.disabled = 1
 sys_language_uid.disabled = 1
}

i also do hide fe_group access dropdown and the system´s language selector thus making the backend experience more simple.

keep TYPO3 sysfolders clean

Posted on by
1

just a small hint to restrict the creation of new elements inside a page (eg. a sysfolder) so that this sysfolder will only hold tt_news entries or sys_templates or whatever. you put that code into the pageTS of the sysfolder/page:

mod.web_list.allowedNewTables := addToList(sys_template)

if you´d like to only contain tt_news entries and tt_news categories you´d put addToList(tt_news,tt_news_cat) into the TS and then these are the only elements to create new inside that folder. if you want the sysfolder to hold only entries for the nifty contagged extension, you use addToList(tx_contagged_terms). here´s more on contagged as tool tip manager.

t3 version 4.4alpha backend without css and js

Posted on by
1

just solved another mystery that was dazzling my mind on a small project regarding TYPO3 version 4.4 alpha2 where the frontend worked like expected but the project code (that was updated from version 4.2.6) showed an ugly distorted backend.

all styles and javascript functions were gone!

i cleared any temporary data collection, checked rewrites, paths, everything was ok. i reloaded the sources :-) but it did not change anything. but when i started to delete all those extension corpses in typo3conf/ext/ i got one idea. extension pmktextarea integrated okay in backend in former t3 installations… and as i saw, it still did and somehow seemed to overwrite essential js for the backend. deleted the folder, cleared the TEMP* files in typo3conf/ and reloaded the backend. worked. phewww…

The requested page didn’t have a proper connection to the tree root

Posted on by
1

Just a fast snip i was hunting today:

It might be helpful to you, if

  • you use RealUrl
  • get the errors after following links to pages what definetely are correct and visible
  • the errors shows “mp vars”

Get yourself the ‘realurlmanagement’  extension and list the pages in backend hat are the target of the links with it (use ‘pages’ option in module´s view)

The extension may show you several different paths to your page. Just flush them all and you´re good to go.

I was searching for user errors on a larger system for an hour, and did check the realurl caches at last.

And if you´re here but the above solution is not working for you, check the first obvious thing in your shortcut / linking page:

Did you specify the target page? :-)

Backend View

get user ip from behind reverse proxy setup

Posted on by
Reply

small problem, wide reach. if your TYPO3 is set up behind a reverse proxy (like pound) and you need the ip connection information of the visitors, T3´s userfunction method comes in handy.

fileadmin/scripts/fwdip.php


<?php
class user_fwdip {
 var $cObj;
 function main($content,$conf){
  $ip=$_SERVER['HTTP_X_FORWARDED_FOR'];
  return $ip;
 }
}
?>

This is the file you´d like to ask for the ip from within TYPO3.

To be able to use this file in a userfunc style you´ll need to include the file in TypoScript, i put it into an own TS template on one special page.


page.includeLibs.fwdip = fileadmin/scripts/fwdip.php

You now could put the stuff on the same TS template but i recommend this neat extension to generate the output to one special page in a content element. The extension wraps the TS in a COA.


20 = USER
20 {
 userFunc =user_fwdip->main
}

Now the page you put the element on should show your real ip address, instead of the proxy ip.

Simple, but fully worth a snippet.

nice TYPO3 extensions

Posted on by
Reply

just wanted to post five neat extensions you can get freely from the TER i find worth to be mentioned since they really give me no headache but useful features:

  • stg_clearcache
    allows you to clear cache of user-owned branches in one big installation, so it’s not only clear cache of this one special page and also not clear all page cache. useful if you run a large system or microsites.
  • kb_filequota
    allows you to have a quota on filemounts, either by giving a size limit on the filemout itself or for each user. useful if you’d like to save space and suppress waste in the filemounts.
  • rscliem
    allows you to automatize the extension updates on your system. i use it as nightly extension-cache update and it notifies me by mail, if extension should be updated for the very TYPO3. useful if you’d like to take steps in automatic administration.
  • realurlmanagement
    allows you to view and manipulate a lot of stuff relating to RealUrl extension. simple alias and page-path editing. useful if the system works with RealUrl.
  • nc_staticfilecache
    allows you to cache the pages from your system to server disk and serve them from there (waaay faster!) and so have the site up and running even if the your TYPO3 is ill. useful, if you have mostly static pages and mod_rewrite going.

even if some of them might be well known, i wanted to put a link to give the extension authors a big up! yeah great stuff, keep on going!

if you think this short list was helpful, just leave a comment. i would appreciate, if you send me your missing extension entry for here ;-)