Below are slides from my talks at developer days. These are not a typical presentations with a lot of words on slides. In future I will also publish PDFs with texts explaning every slide.

Writing secure code

How to become a better programmer

Page browser is a complex piece of code. It is often tricky to have it done. An example from the iStockPhoto below shows that clearly...

I like TypoScript! It is a fantastic language. Almost everything is possible. For example, today I had to solve an interesting task. I have to show keywords on the page. Keywords shouls be taken from the page's "Keywords" field and appended by the content of a TypoScript constant. Any of these too could be empty and there should be no extra comma if one of parts is missing. If no keywords are set, there should be no keywords meta on the page.

Here is how I solved it...

cHash is one of the most mysterious and misunderstood parameters in TYPO3. There are several articles about cHash on the web (including my own) but it still remains a mystery.

cHash is important for proper caching in TYPO3. Therefore I decided to write when you need it and when not.

There is a new web site dedicated to the TYPO3 security. It is created and managed by Marcus Krause, who is the most active TYPO3 security team member. Marcus is known for his strong position about security, his dedication to this work and attention to details.

I highly recommend this new site to anyone who is interested in TYPO3 security.

So we are on the round 3! Many people did very well on both previous rounds. Everyone was able to see at least two problems, some counted 4, 5 or even more. Some of "problems" were not "problems" but "possible enhancements".

I must tell that I decided to put a little catch in the game The catch was a "print" parameter. Many people immediately remembered that it is used in TemplaVoila and felt for this Now I have to tell that there is no TV involved! Original TS was said to be complete, so there is...

If you liked part 1 of the TypoScript error game, you can proceed to part 2 now In part 2 we list all errors we found. Please, try not to watch what other wrote before you post your own list! Do not post solutions yet, please! Just lists errors that you see. This way anyone less experienced can try to fix them before gurus post their solutions.

The game also goes in the TYPO3 mailing lists (English list): part 1 and part 2.