All page names need to be in English.
en da  de  fr  it  ja  km  nl  ru  zh

T3Doc/Extension Builder/Using the Extension Builder

From TYPO3Wiki
Jump to: navigation, search

<< back to Extension Builder main page

Using the Extension Builder

This documentation is outdated!

See for an up-to-date version

Starting a new extension

To create a new Extension, go to the Domain Modelling view. Open the left pane by clicking on the small arrow and enter a meaningful Extension name, a Vendor name (UpperCamelCase) and an extensionKey (without spaces and in lowercase). If you want to create an extension that generates output in the frontend create a plugin with a meaningful name and a lowercase key without spaces. If you want you can add a person that will be listed in the generated files as author.

1. Model the domain

Then create at least one model by dragging it from the grey button "New Model Object" to the canvas. Give it a meaningful name starting with an uppercase letter.

Open the Domain Settings and check Aggregate root if this model is the root of the other models you need. A simple way to find out, if a model is an aggreate root or not, is to consider if you can retrieve objects of this model by requesting them from another model or not. So if you create a post Model and a Blog model, it is obvious that the Blog is the aggregate root and the post is not. You can retrieve posts by requesting it from the blog model: $Blog->getPosts().

To decide if your Model is an Entity or Value object you can ask, if the model has some kind of "identity". Value objects have no identity, they are completly defined by their value. An object defining a color can be called "Blue" but it makes no sense to have multiple instances of this "Blue". If you are not sure, leave this setting on entity.

Open the action panel and select the options you need. All actions you select will be configured as allowed actions for your plugin.

+++++++++++++++++ Security check!! +++++++++++++++

Be aware that any action can be called just by adding a param to the URL where the plugin is included. If you provide an edit/update action link it will look like this:[action]=edit&tx_extensionkey_pluginkey[profile]=12

This will load your edit view (wich contains a form to edit the profile) and load the profile data into it. If someone manipulates this URL to look like this:[action]=delete&tx_extensionkey_pluginkey[profile]=23

This would delete profile 23 if you forget to implement access checks or other appropriate constraints.


2. Add properties

The names of properties of the same model have to be unique, they must start with a lowercase letter, should only contain alphanumerical character and should be written in lowerCamelCase if neccessary. The description you enter here, will appear in the backend as help text near the property field.

3. Add relations

If you create multiple models you may want to connect them by relations. A relation should have a lowerCamelCase name like properties and can be connected to the related model by dragging the mouse from the round connector at the relation property to the connector at the top of the related model. You should always open the "more" panel to define what kind of relation you want. These relations are possible:

  • 1:1* means you have one property in your model representing one specific object of the related model.

For example if you say a person has only one account and that account is not used by anyone else you can define it as 1:1.

1:1 Relation in BE Form
  • 1:n* means you have a property in your model representing multiple objects of the related model but each of them has no other relation.

A blog has multiple posts, but each post only belongs to one blog.

1:n Relation in BE Form
  • n:1* means you have a property in your model representing a single object of the related model, but the related model can have multiple relations

For example, each person has a certain place of birth, but many people can have the same place of birth.

n:1 Relation in BE Form
  • m:n* means the property of your model consists of multiple objects of the related model.

For example a book can have multiple authors and each author has written multiple books.

m:n Relation in BE Form

Besides that you can decide if you want to edit the related objects in the backend "inline" that is in the form of the "parent" object or as a select field.

4. Create a plugin

If you want a plugin for your extension, you have to add a plugin in the left panel of the modeler (See screenshot at the bottom of this page)

5. And/Or create a backend module

If you want a backend module for your extension, you have to add a backend module in the left panel of the modeler (See screenshot at the bottom of this page)

6. Save the extension

If your model represents the domain you wanted to implement you can hit the "Save" button. The Extension Builder generates all required files for you. Have a look to typo3conf/ext/"yourExtensionKey" to see the generated files. Now you can start implementing your logic.

Next step: Modifying and extending the model

Category:extension development