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…

typo3 update to 4.3.3

all systems nominal. TYPO3 is now available in version 4.3.3 and it was easy to update for all of the projects i´m responsible for that where on 4.3.x already. good work, coredevs! looking forward to meet you at the t3dd

the changelog can be found in the TYPO3 wiki. the source can be found on sf.

my systems run without any changes. so just put the symlink to the right directory and the system is safe once more.

why update anyway?

you may delay ignore update, if following conditions are met.

  1. If you use TYPO3 in version  4.3.0, 4.3.1 or 4.3.2 (+ development releases of 4.4 branch).
  2. at least one of following PHP configuration variables set to “off”:
    • register_globals (“off” by default, advised to be “off”),
    • allow_url_include (“off” by default)
    • allow_url_fopen (“on” by default)
  3. You are using Suhosin and haven’t put URL schemes in configuration variable ”suhosin.executor.include.whitelist”.

these details were taken from the current security bulletin. TYPO3 is also a that good cms because the security team does their job that good.

piwik in version 0.5.2 + update script

while waiting for an almost ten gigabytes large piwik database to be updated, i’m just writing down that piwik got a new release yesterday.

upgrading piwik is easy. i pushed all steps to upgrade it on a linux (debian) server in a small shell script you may find useful.

simple update script for piwik

#!/bin/bash
# auto-update piwik
# @author bigbabou <bigbabou@web.de>
#

# where my current piwik resides
installdir=/var/www/

# where the ugly stuff should be made
workingdir=/home/bigbabou/

# used for copying the new piwik source
piwikdir=/home/bigbabou/piwik/*
logfile=updatepiwik.log

# where the new piwik can be downloaded
piwikurl=http://piwik.org/latest.zip

cd ${workingdir}

# check if update is necessary
wget -N -o${logfile} ${piwikurl}

# overwrite silently
unzip -q -o latest.zip

# tidy up old piwik dir
cd ${installdir}

rm -rf core js lang libs misc plugins tests themes tmp
rm index.php piwik.js piwik.php robots.txt README

# safe global.ini before updating
chown root config/global.ini.backup_by_script
chmod 770 config/global.ini.backup_by_script

echo 'copying new files'
cp -r ${piwikdir} .
chown -R www-data *
chgrp -R www-data *
ls --color=auto -lA ${installdir}

# make nightly precaching exectuable
chmod 770 ${installdir}'misc/cron/archive.sh'

# clean up stuff
cd ${workingdir}
rm latest.zip
rm How\ to\ install\ Piwik.html
rm -rf piwik

echo 'piwik update successful. have a nice day!'

## update db on shell
php ${installdir}index.php

echo ' - update script end -'
exit 0

two lines could be added for convenience

chmod 777 ${installdir}tmp/cache
chmod 777 ${installdir}tmp/templates_c

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.

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!

mysql replace http://typo3/http://

remember when the links out of the rte looked like http://typo3/http://yourlink.tld/ ? well, as i still prod at links looking like this, i’d rather post the relieving sql statement here. it’s simple but handy. the replace function just makes backend work even faster.

UPDATE tt_content SET bodytext = REPLACE(bodytext, 'http://typo3/http://', 'http://');

TYPO3 Unknown column error

Little problem after update to TYPo3 4.3 alpha3 i.e. with domain entries. After changing the domain record for a site (in a multi domain tree setup) the following error is displayed:

SQL error: ‘Unknown column ‘redirectHttpStatusCode’ in ‘field list” (sys_domain:3)

Simple solution: go to tools>install enter the password and start the database analyser and let the compare module do it´s job. after that, most problems like the above should be gone. consecutive action might be the db check>Check and update global reference index.

For most, it is obvious that the compare module is the successional move to finish the incremental update. But if you forget, you might find that blog post. things done ^^

t3dd09

t3dd

just in time for the TYPO3 developer days 09 I kicked my X so badly that there was no other option to reinstall the system, so I could have a graphical user interface. But after having installed Zenwalk again, the thing “flows”. Now the talk for programming secure extensions is going to start – I’m excited to learn stuff. More to come, as long the wifi keeps working.

Remember that they only set up one grill for all of us? Lucky me coud grab the pieces very fast, but see the grill ready queue adding up @ T3DD09:

steakschlange

Update: my notebook´s hdd crashed at the T3DD so, bah! Tough: All data, all music… simply flushed away.

The event was still very exciting, and i´m very looking forward to attend another TYPOrhythm party.