use php5-xcache

if you run ordinary setups for php think about using the xcache opcode cache. it will make your TYPO3 backend and frontend faster.

while this knowledge is wide spread, i´d like to express my feelings about a very responsive t3 backend after giving more meat to the xcache size. put 80Ms there. xcache comes with a nice admin log which shows the cache hits and misses, here are the explanations.

the t3 backend (the newer the better) is lightning fast even on larger installations (hundreds of editors) due to high cache count of necessary php files. uhm, and before i forget: of course the database server must be cool, too — or you will wait for the queries to be finished and thus all the php engine speed would idle around.

soundtrack for worQ – 08/10

It´s about time to put you three more techno emeralds into the browser. you decide whether you click (take the colored pill) or whether you leave (because you´re not 18 or older).

koxbox – the great unknown

check this funny vid out and hear by yourself what´s the deal of good psytrance. digging into ontologies.

sleeparchive – research

this is what i do. research. this is the soundtrack to my every action. and it´s also greatly mixable 10 of 10!

holgi star & miro pajic – oldschuhe

good grooving basslines and a perfect shuffle make this track a lovely tool for the feet while the fingers keep flying over the keyboard. a head nodd of it´s own kind. enjoy the clowns.

soundtrack for worQ – 04/10

First of all: Luke Slater´s new masterpiece. I selected the most annoying track from it, because this is such a great mess for my brain when programming.

grooves and shuffles ftw… Uto Karem

and one more classic techno smasher pump panel´s ego acid… because it reminds me of nice parties had back then…
Did McDonald’s make this tune? Cause I’m lovin it!

successful arrival in 2010

happy new year to everyone!

i’m wondering what kind of evil spirits we try to excorcize with the thousands of bangs but they sum up to the unique sound of the new year. and that’s okay, even i do not take part in skyrocketing my money. hopefully you all had a nice midnight experience and were sound and sane.

the numeric visible style of 2010 is just nice, don’t you think? i liked 2001, too and… who knows… 2100 as well.

typo3 4.3 up and running

most of my projects are updated and as expected the update to TYPO3 4.3 hadn’t been a problem. everything went well and the new backend look is charming.

all went well

the sites get even faster,i did not instatiate the new caching factory, though. the new recycler is great and a must for every mid sizes website. the new recycler works way better when deleting tons of entries from a table.

the update of the extension templavoila to version 1.4.1 was also no problem, though on the biggest site i administrate (with more than 60 backend editors) i’m preparing for some bug reports. newest tv style finishes the new interface design at all – a feature that impresses them all is the drag and drop feeling.

tt_news 3.0.0 – don’t update live

but beware of upgrading tt_news too fast from version 2.5.2 (which is the highest in the 2.x branch) to 3.0.0 if you not have checked how the templates change! the whole morning was consumed by the fixing of tt_news styling. tt_news come with new caching mechanism that promises to speed up some data work that needs to be done every time news are rendered. tt_news 3.0.0 comes with that cool new update script that checks for possible problems – where it removes relations to templates as far as i remember.

falling back to the standard template coming with v3 the title wrapping changed from h3 to h2 and stuff like this – thus breaking the layout of the website on every page. if you’re using tt_news as main function for a big web site that should not be done “live”. ;)

also there had been problems in the realurl configuration after the update. solution was to grab a selection of the content of res/realUrl_example_setup.txt in the tt_news ext folder and drop it in typo3conf/realurl.php and so the errors were gone.

i don’t know why this was necessary, but tt_news showed a nasty red bordered error if now singlePid was set (which can be done in the constant editor) even if the site worked before with tt_news 2.5.2 due to single-page target was set per plugin settings.

another thing you might want to avoid is the output of some php stuff before the website’s head section.

all in all i’m happy away how simple it’s getting to create web content management. many of the tricks you need to learn are now turned into guides (i.e. compare database is the final step of the update in form of a button in the update wizard process – before that you just “needed to know” that).

great job TYPO3 core team!

from brasero to gnomebaker

my ubuntu 9.10 held back a suprise for me to release it to me this sunday morning. brasero does not burn dvds anymore. it just gets stuck while ‘getting size’ and stays there in a loop. after almost an hour it had to be canceled. as brasero is a veeery simple burning tool, i’m sure i used all meaningful combinations of options i could set per gui.

Bildschirmfotosince it is weekend and i couldn’t find an appropriate solution for this problem, i installed gnomebaker which seems to do a good job right now. it looks way better than the ultra-simple brasero interface. funny thing is that i got the Brasero error log shown only after starting to burn with gnomebaker – quite odd but hey, now it’s here. and to make this post a bit bigger, and to bloat the internet with some information i don’t know somebody could make use of, and to just have it pasted somewhere… here it is:

Checking session consistency (brasero_burn_check_session_consistency brasero-burn.c:1848)
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI called brasero_job_set_output_size_for_current_track
BraseroBurnURI stopping
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI called brasero_job_get_session_output_size
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI called brasero_job_get_current_track
BraseroBurnURI no burn:// URI found
BraseroBurnURI stopping
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_set_output_size_for_current_track
BraseroLocalTrack stopping
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_get_session_output_size
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_get_current_track
BraseroLocalTrack no remote URIs
BraseroLocalTrack stopping
BraseroGrowisofs called brasero_job_get_action
BraseroGrowisofs getting varg
BraseroGrowisofs called brasero_job_get_action
BraseroGrowisofs called brasero_job_get_current_track
BraseroGrowisofs called brasero_job_get_flags
BraseroGrowisofs called brasero_job_get_speed
BraseroGrowisofs called brasero_job_get_device
BraseroGrowisofs called brasero_job_get_action
BraseroGrowisofs called brasero_job_get_session_output_size
BraseroGrowisofs called brasero_job_get_current_track
BraseroGrowisofs called brasero_job_get_fd_in
BraseroGrowisofs Using genisoimage
BraseroGrowisofs called brasero_job_get_current_track
BraseroGrowisofs called brasero_job_get_tmp_dir
BraseroGrowisofs called brasero_job_get_action
BraseroGrowisofs called brasero_job_set_current_action
BraseroGrowisofs got varg:
growisofs
-use-the-force-luke=notray
-use-the-force-luke=4gms
-dvd-compat
-speed=4
-use-the-force-luke=tty
-Z
/dev/sr0
-dry-run
-r
-J
-input-charset
utf8
-graft-points
-path-list
/tmp/brasero_tmp_6OU33U
-exclude-list
/tmp/brasero_tmp_S2T33U
-print-size
BraseroGrowisofs Launching command
BraseroGrowisofs called brasero_job_get_fd_out
BraseroGrowisofs stdout: Executing ‘genisoimage -r -J -input-charset utf8 -graft-points -path-list /tmp/brasero_tmp_6OU33U -exclude-list /tmp/brasero_tmp_S2T33U -print-size | builtin_dd of=/dev/sr0 obs=32k seek=0′
BraseroGrowisofs called brasero_job_set_dangerous
BraseroGrowisofs stderr: Total extents scheduled to be written = 2285751
BraseroGrowisofs called brasero_job_get_action
BraseroGrowisofs called brasero_job_set_output_size_for_current_track
BraseroGrowisofs Finished successfully session
BraseroGrowisofs stopping
BraseroGrowisofs got killed
BraseroGrowisofs called brasero_job_get_action
BraseroGrowisofs getting varg
BraseroGrowisofs called brasero_job_get_action
BraseroGrowisofs called brasero_job_get_flags
BraseroGrowisofs called brasero_job_get_speed
BraseroGrowisofs called brasero_job_get_device
BraseroGrowisofs called brasero_job_get_action
BraseroGrowisofs called brasero_job_get_session_output_size
BraseroGrowisofs called brasero_job_get_current_track
BraseroGrowisofs called brasero_job_get_fd_in
BraseroGrowisofs Using genisoimage
BraseroGrowisofs called brasero_job_get_current_track
BraseroGrowisofs called brasero_job_get_tmp_dir
BraseroGrowisofs called brasero_job_get_action
BraseroGrowisofs called brasero_job_get_data_label
BraseroGrowisofs called brasero_job_set_current_action
BraseroGrowisofs got varg:
growisofs
-use-the-force-luke=notray
-use-the-force-luke=4gms
-dvd-compat
-speed=4
-use-the-force-luke=tracksize:2285751
-use-the-force-luke=tty
-Z
/dev/sr0
-r
-J
-input-charset
utf8
-graft-points
-path-list
/tmp/brasero_tmp_AUQ23U
-exclude-list
/tmp/brasero_tmp_2PQ23U
-V
Data-CD/DVD (29 Nov 09)
-A
Brasero-2.28.2
-sysid
LINUX
-v
BraseroGrowisofs Launching command
BraseroGrowisofs called brasero_job_get_fd_out
BraseroGrowisofs stderr: :-( /dev/sr0: failed to grab associated sg device
BraseroGrowisofs stdout: HUP
BraseroGrowisofs stderr: HUP
BraseroGrowisofs process finished with status 144
BraseroGrowisofs called brasero_job_error
BraseroGrowisofs finished with an error
BraseroGrowisofs asked to stop because of an error
error        = 0
message    = “no message”
BraseroGrowisofs stopping
BraseroGrowisofs got killed
Session error : unknown (brasero_burn_record brasero-burn.c:2811)

Even though i switched to gnomebaker, i’m still interested what the problem is and how it can be solved. is it just the wrong type of media i’m using? For now, i’m off for the sunday… waiting for a patch :-)