Book Image

TYPO3 Extension Development

By : Dmitry Dulepov, Adrian Zimmerman
Book Image

TYPO3 Extension Development

By: Dmitry Dulepov, Adrian Zimmerman

Overview of this book

Table of Contents (13 chapters)


This is the first book in English to cover TYPO3 extension development in detail. The author is a member of the TYPO3 core team and developer of many popular TYPO3 extensions. Both novice and experienced TYPO3 programmers can use this book to build the extension they need following best practices and saving a lot of time that would otherwise have been spent pouring though the documentation.

The book is structured so that following the chapters in order builds a TYPO3 extension from the ground up. Experienced developers can use individual chapters independently to get only the information that they need.

Each chapter is divided so that the first part contains a description and discussion of the topic covered followed by a coding example with an explanation of how principles and techniques from the first part are followed in the code.

The reader is encouraged not only to read the book but also to look into the discussed classes and actually code the extension while reading the book.

What This Book Covers

Chapter 1 gives an overview of the TYPO3 API and tells about the most important classes in TYPO3.

Chapter 2 describes files in the TYPO3 extension, what role they play and how to use them.

Chapter 3 focuses on planning. Planning makes extensions better. It makes the project successful.

Chapter 4 walks the reader through the process of extension generation. All options are explained, several issues are pointed out, and useful tips provided.

Chapter 5 focuses on the Frontend plugin theory. It also provides a lot of tips to make extensions effective.

Chapter 6 is dedicated to practical progamming. The reader will see how to make list, search, and single views, use AJAX from the Frontend plugin, and create useful TypoScript for the plugin.

Chapter 7 focuses on the Backend module programming.

Chapter 8 describes how to write documentation for the extension and polish the code before releasing it to TER.

What You Need for This Book

The author assumes that the reader has the following knowledge:

  • PHP programming The reader is expected to have some experience with PHP and knowledge about PHP classes in general. No prior TYPO3 programming experience is needed.

  • TYPO3 as an administrator Basic knowledge of TYPO3, TypoScript, and TYPO3 extension idea.

  • TYPO3 documentation The reader should know what is TSRef, TSConfig, TYPO3 Core API. The reader should be able to find these documents in the Documentation section of the website.

  • Basic knowledge about phpDoc.

Who is This Book For

This book is for PHP developers who want to develop a TYPO3 extension. It assumes the reader has experience with PHP, XML, and HTML. No prior knowledge about TYPO3 extension programming or the TYPO3 API is presumed.


In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.

Code words in text are shown as follows: " Notice how param1 is passed as a value first and then as an array by using a dot."

A block of code will be set as follows:

plugin.tx_myext_pi1 = USER
plugin.tx_myext_pi1 {
userFunc = tx_myext_pi1->main

When we wish to draw your attention to a particular part of a code block, the relevant lines or items will be made bold:

plugin.tx_myext_pi1 = USER
plugin.tx_myext_pi1 {
includeLibs = EXT:myext/pi1/class.tx_myext_pi1.php
userFunc = tx_myext_pi1->main

New terms and important words are introduced in a bold-type font. Words that you see on the screen, in menus or dialog boxes for example, appear in our text like this: "To finish this step, press the Update... button".


Warnings or important notes appear in a box like this.


Tips and tricks appear like this.

Reader Feedback

Feedback from our readers is always welcome. Let us know what you think about this book, what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.

To send us general feedback, simply drop an email to , making sure to mention the book title in the subject of your message.

If there is a book that you need and would like to see us publish, please send us a note in the SUGGEST A TITLE form on or email .

If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on

Customer Support

Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.

Downloading the Example Code for the Book

Visit to directly download the example code.


The downloadable files contain instructions on how to use them.


Although we have taken every care to ensure the accuracy of our contents, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in text or code—we would be grateful if you would report this to us. By doing this you can save other readers from frustration, and help to improve subsequent versions of this book. If you find any errata, report them by visiting, selecting your book, clicking on the let us know link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata added to the list of existing errata. The existing errata can be viewed by selecting your title from


Piracy of copyright material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works in any form on the Internet, please provide the location address or website name immediately so we can pursue a remedy.

Please contact us at with a link to the suspected pirated material.

We appreciate your help in protecting our authors, and our ability to bring you valuable content.


You can contact us at if you are having a problem with some aspect of the book, and we will do our best to address it.