zoe.vc

A while ago I wrote an article about a script I created to backup databases. Since then I had to make little changes and decided to put it to Google code as Open-Source-Project and released the new version 0.1.1 with some minor changes.

If you're interested in the script, head over to its project page and check the appropriate pages like the Changelog and the Installation and Requirements page. Feel free to download and comment  it.

There are a few nice tipps in the blog of Dmitry Dulepov to speed up the Typo3 performance you should have read. #2 was unknown to me so far.

Also jedes mal, wenn ich eine mehrsprachige Typo3-Seite erstellen, komme ich durcheinander mit den Sprachen. Und ich vergesse jedes mal, wie man einem Frontend-Plugin sagt, dass es die durch $this->pi_getLL($key) ausgegebenen Texte lokalisiert. Und das geht so:

class tx_extkey_piX extends tslib_pibase {
   function main() {
      $this->sys_language_uid = (int) t3lib_div::_GP('L');
      ...
   }
}

Manchmal ist es nötig, die Datenbank von Typo3 auf UTF-8 umzustellen, da man arabische Zeichen oder was auch immer speichern will, und wobei die Kollation der Datenbank latin1_swedish_ci, mit der sich Typo3 standardmäßig installiert, nicht taugt.

Dazu habe ich diesen nützlichen Blogeintrag von Markus Giesen gefunden: Typo3 mySQL-Datenbank auf UTF-8 umstellen bzw. konvertieren

Jedoch ist bei mir im Export nie die Kollation festgeschrieben, diesen Schritt konnte ich de facto überspringen. Auch hatte ich keinen phpMyAdmin, also mussten die Kommandos für die SQL-Konsole zum Anpassen der Kollation her:

Anzeigen der verfügbaren Kollationen auf dem Server:

SHOW COLLATION
SHOW COLLATION LIKE 'utf%'

Ändern der Kollation der aktuellen Datenbank:

ALTER DATABASE DEFAULT COLLATE utf8_general_ci

Und danach weiter nach Markus Giesens Anleitung verfahren und alles wird gut

I'm currently getting into the Symfony framework and I can definitly say that I like it.

But as my site was finished after only some hours I had a problem concerning the display of special characters like the umlauts (ä, ö, ü) aso. I don't use a database created by SF/Propel but use an existing one with latin1_* encoding (the default TYPO3 db encoding). Unfortunatly all umlauts where displayed as questionmark so I started finding an solution. The characters are fuzzy because they were not correctly returned by propel. I tried all configuration directives I found (setting the encoding of the connection to utf-8 aso) but nothing worked.
Finally I found a snippet that fixes the problem for me: Setting UTF-8 for Propel with MySQL tables and now everything is just fine!

As I'm currently validating different lightbox clones I'll advert to the brilliant "The Lightbox Clones Matrix" of PlanetOzh. It lists nearly all lightbox clones and gives the possibility to filter by features and used javascript framework. File size is displayed, too.

The Lightbox Clones Matrix

Unfortunatly there is no working and official version of the PDT release for the current Eclipse release, Eclipse 3.4 Ganymede. However it is possible to use both. I found the solution within the Digital Base blog: Simply download the nightly build of PDT and integrate it as local site in the Eclipse update manager and then install. Quite easy.