After some time of silence it was time for an update on my advanced sitemaps extension. It took a while but all open bugs and feature request have been processed, and I'm proud to announce that version 1.1.0 of this extension is now available from the TER.

Many times, when taking a short peek through new extensions in the TER, I find plenty of extensions that use PHP's native MySQL functions to access the database. In my previous post I already described why this something wrong, and why you should avoid it. In this article I will show you how it should be done, and how you can write less and cleaner code by doing so.

While developing and reviewing TYPO3 extension, you occasionally come upon pretty funny and sometimes disturbing stuff. At some point we all have to learn new things. So we can't expect it all to go right and well from the start.

Some days ago I got a request from someone who was interested in my code snippets plugin. At that time I couldn't really offer the extension, it was simply too specific for my own website. Now that I've made some changes, I feel more comfortable with making it public.

Sometimes, the normal approach for adding extra fields to a table will just not do. For example, if you don't really know what the other table is going to be. I came across this challenge some days ago. I was working on my sitemaps extension and wanted to have some nice options to use inside Google Sitemaps. To keep it flexible I didn't want to predefine the tables. So how do we add fields to a table, without actually adding them to a table?

Most extension developers deal with this little image for their extension, others don't. With over 4500 extensions in the TER, theres also quite the variety of icons to be found. Let's have a closer look at those icons.

Since I there are several people who frequently comment in my blog articles, I thought some kind of white list for these people would be a good idea. This would save me some time, so I wouldn't have to approve all their comments. This didn't exist in t3blog yet though..

When designing and creating cool and fast web applications, a technique called AJAX is commonly used to provide the user with a nice and smooth workflow. It allows the user to get new information from the server-side, without having to deal with page reloads. TYPO3 has some cool features that allow you to easily combine AJAX with TYPO3, to make awesome web applications.

When using TypoScript we often have to work with objects like TEXT, HTML, COA.. you name it. Some developers store their objects inside lib., others will use temp.. But what's the difference? And when should you use the one, and when the other?

In this article I will explain how to bypass the table restriction that was made for CONTENT objects. This restriction is made for security reasons, however I wonder how useful it is since it's so easy to bypass.