Long time no see… yes, business is keeping me away from all the fun stuff. I’m currently working on cleaning up and then extending mm_forum, and of course the TYPO3 core.  Last week, I visited Jeff in Dallas and we had a good run digging into some serious XML issues with libxml2 and expat (See http://bugs.typo3.org/view.php?id=9359) and we also looked into over 20 patches floating around in the TYPO3 core list.

Yesterday I spent some time working on my seo_basics extension and on the last fixes for the upcoming DAM (Digital Asset Management) version 1.1 — a beast of an extension,  but good for adding metadata to uploaded files. While there was a huge movement in May and June, things kinds slowed down in the last months, and Ben pushed the whole thing a bit more. In any case, 1.1 will be a bugfix release (with a dependency on TYPO3 4.2.2 or later) marking the way for a glorious 1.2 (Release TBA ;-)). more…

If you have to customize a TYPO3 installation for your editors, and you use tt_news, you maybe have had the problem. Your editor gives you a call and let’s you know that he can’t see his just finished news in the frontend. You find out that the record is not hidden, but the problem is that the editor hasn’t had a category selected. Most likely it’s because the categories are on the second tab in the TCEforms. (in some cases where we “misue” tt_news, it’s the only thing that is on the second tab). However, the problem is then that the editor saves the record and forgets to attach a category to it. With this simple statement you can force the editor to select a category:

TCEFORM.tt_news.category.config.minitems = 1

This can be done on pagesTSconfig level but also on userTSconfig, and is quite helpful to save some support calls.