Dringend gesucht: Ein gescheites Portfolio.
Weshalb ich jetzt auf die Schnelle die Beta-Version von UI 1.5 live geschaltet habe.

In den nächsten Wochen wird das Ganze dann finalisiert.

Yet to do:

• Gescheiter Bugfix für die fehlerhafte Darstellung der Subnavigation im Firefox (derzeit nur Quick'n'Dirty-JS-Hack)
• Journal: entweder blueprintCSS rausschmeißen oder Bugfix finden für das merkwürdige Verhalten des Footers (siehe ebenda)
• Journal: Visuelle Anpassung an die restliche Website abschließen (u.a. noch nicht gestylt: Kommentare, Einzeleintrag, Links suboptimal)
• Kontaktformular: Umstellung auf SFM 2.0
• Portfolio: Fehlende Bilder einbinden
• Portfolio: TimThumb mit IM Wrapper ersetzen

Thanks to some malfunctioning plugins, this Habari install was out-of-order for nearly a month.

I've been working with the "un"stable version on my private weblog, but havent discovered particular unstability so far. Sometimes, of course, there was a bit of crashing and so on, but soon to be stopped by either uploading older files or the latest data out of the "alternative download" (habari_head.zip).

Looks like of some changes were done to the core, thus some plugins stopped working properly. In particular, I removed one plugin (pingback) and disabled another one (tagcloud), latter one did work correctly till this very PHP memory allocation error started occuring, directly after installing the so-called "stable" version update 0.5.1. :-/

I originally wanted to stay up-to-date, but use the stable builds, but now, I'm going to stick with the allegedly unstable alpha releases instead, to avoid getting into another "no way to blog about my work"-situation as described above.

A small plea from my side: Please, whoever is building or deciding about if a version is ready to release - give it a litttle bit more of testing in a normal environment, ie. a hosted solution, NOT your personal server. I cannot recommend anyone to use Habari if this goal - getting Habari to run under normal conditions - isnt met accurately! :-/