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.

slept well?

recently i reactived my smartphone from it´s oblivion and hence all the mobile activities were a bit cutoff during the last weeks. let me say months, but that was not only the issue with the smartphone. damn cell battery is becoming weak a half year after purchase.

i thought about the virtual effigy most people produce. fortunately, my activites mostly stay controlled and no excessive drinking bout became evident (afaik) in the network (right now). don´t know if that is the main aspect of data security but the trail we leave in the sand is quite persistent. wow, i just wanted to write down that my blog is underpopulated which is a pity, and i end up contemplating about the virtual identity issue.

give me a few posts to habituate myself to blogging. nevertheless, i´m cool with 1-to-n communication (where n includes you, whether you´re bot or human). leaving us defining when an entitity will be able to extract the semiotic meaning of itself, i´d rather go now and have some real life – beginning with a tasty shisha.

and i hope my smartphone will at least stand by for the next few hours, calling that a “milestone”.

t3 version 4.4alpha backend without css and js

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…

how got my ethernet disk interface access back

fancy stuff to do with an lacie ethernet neil poulton disk 500gb item

network space

And i just wanted to reset the admin password of the lacie web interface due to froob-style loss. for those seeking a quick answer for that:

  • turn OFF your ethernet disk (if it’s running now). after the light stopped flashing…
  • turn it ON again for around 2-3 secs and…
  • turn if OFF again and prepare to…
  • turn it ON immediately. Now the blue light is flashing frenzy and you’re about to be able to log into the interface with admin/admin

You see, no need to be a geek to gain access to an ethernet disk standing around ^^

tt_news 3.0.0 outputs “?>”

the extension update yesterday was not as simple as i thought and what happenened when i came to work today? tons emails complaining about broken web layout in frontend. ha! it’s a pity, the extension is really a good piece of code – but in one file the php ending tag was appearing twice. this generated a ?> just before the output of TYPO3 ( the doctype declaration and else ).

after finding out that it definitely was tt_news i quickly found the bug in the bugtracker :)
alywas look in the bug tracker first.

and the solution is that simple:

in typo3conf/ext/tt_news/lib/class.tx_ttnews_cache.php remove the last line (which is the doublette “?>”) and the system does not print out that tag before the website begins.

but still, it’s a pity that firefox again handles even this error and displays the website the first time after clearing cache with the ?> and the next times without it. But the internet explorer is as dumb as we expect it to be. broken layout due to malformed code – no css inclusion.

search and replace mysql

simple to do if you know how it’s done. and instead of searching the web, i’ll stick to my own note from now on :)

UPDATE tablename SET fieldname = REPLACE(fieldname,'searchpattern','replacement');

quite useful for batch changes i.e. paths to images that have changed… ;)

it is of importance to not use ” on tablename or the fieldname.

to narrow it down to a special page (like in Backend jobs for TYPO3)

UPDATE tt_content SET bodytext = REPLACE(bodytext, 'http://bigbabou.org', 'https://bigbabou.org') WHERE pid=2501;

that will change every link from http:// to https:// in any content element on page 2501. you could break it down even further to only change CType=’HTML’ (speaking, content elements of type HTML).
easy to apply but nice to have it to copy from…

got fooled?

yesterday was a day that most people use to release stuff that is designed to fool you. the calendar puts this date to april 1st and we call it april´s fool. I just thought about whether or not i am supposed to feel bad about not being trapped with an april joke yesterday. Have you been fooled?

I think it is going to be really fooled in a time where every content is tagged and commented instantly and got the date stamped on it.

Two cool news that got my attention yesterday

  • Twitter switch for Guardian, after 188 years of ink
  • TYPO3 development licence sold – T3DD09 cancelled
  • I think there are a lot of good fooling news out there, I just hadn´t more time to look around – if you have good fooling links, you´re welcome to add them for me as comment.