en	An extension key must have minimum 3, maximum 30 characters (not counting underscores)

en	Illegal character(s) in extension key. Allowed characters are: a-z (lowercase), 0-9 and '_' (underscore)

en	The key may not begin with one of the following prefixes: tx,u,user_,pages,tt_,sys_,ts_language_,csh_

en	Extension keys cannot start or end with 0-9 and '_' (underscore)

en	There is an existing piBased extension with this extension key. Please choose another extension key or rename the existing extension directory

en	Name

en	Key

en	Extension title

en	Extension Key

en	The extensionkey should be lowercase and without spaces. It will be the unique identifier for this extension.

en	Vendor name

en	The vendor name is the first part of the new package identifier

en	Descr.

en	Description

en	Version

en	Target version

en	If your extension uses features of Extbase/Fluid versions higher than 1.3 you can select your target version here. You have to add the dependency manually in the "Depends on" field.

en	State

en	Alpha

en	Beta

en	Stable

en	Experimental

en	Test

en	Category

en	OR custom

en	You can define an own category here

en	The category this extension belongs to in the extension manager.

en	Miscellaneous

en	Services

en	Backend

en	Frontend

en	Templates

en	Examples

en	Documentation

en	Priority

en	This tells the EM to try to load the extension as the very first or last of all extensions. Possible values: top or bottom

en	Shy

en	If the extension is marked as shy, it won't be displayed in the extension manager by default

en	Disable versioning

en	Check this if your extension needs no support for versioning. This will skip the creation of versioning related columns in the database

en	Depends on

en	If the extension is depending on other extensions, enter the extension keys here (one per line followed by a double arrow and the lowest version number). Please leave extbase and fluid since they are required always

en	Persons

en	Role

en	Developer

en	Product Manager

en	Email

en	Company

en	Frontend plugins

en	The frontend plugins which have to be registered in the extension

en	Controller action combinations

en	Here you can configure, which controller action combinations this plugin/module should have. Example: <br />Blog => list,show <br />(one controller per line, actions comma separated) <br />If you leave this empty, all available actions are configured for this plugin.

en	Non cacheable actions

en	Typically create, delete and update actions should not be cached. (Same format as above)

en	Switchable actions

en	Make actions switchable in the plugin's form. One line for the label, one for the list of allowed Controller->action pairs (semicolon separated). Example: <br />Display items<br />Model->list; Model->show;<br />Admin<br />Model->new; Model->create; Model->edit; Model->update;

en	Backend modules

en	Main module

en	Should be unique for this model

en	Type

en	More

en	More options

en	Advanced options

en	Remove

en	Add

en	1:1

en	n:1

en	1:n

en	m:n

en	Is exclude field?

en	If set to true, this field will only be visible for admin users per default

en	New model object

en	Domain object settings

en	Object type

en	Value objects are simple objects that are defined by their value and have no 'identity'

en	Entity

en	Value object

en	Is aggregate root?

en	If true, the extension builder will generate a repository and default controller actions for this model

en	Enable sorting?

en	If true, sorting in the backend is enabled

en	Map to existing table

en	If the model should extend an existing table, you can configure this here

en	Extend existing model class

en	If this model should extend an existing other model, name it here

en	Default actions

en	Action type

en	For each selected action, the extension builder will generate a template and a action method in the controller of this model. If the model is an aggregate root the default CRUD actions will be generated per default.

en	show

en	list

en	new/create

en	edit/update

en	delete

en	Properties

en	Property name

en	The name should be lowerCamelCase and unique in this model

en	Property type

en	All types with * are not yet supported by the frontend form generation/validation

en	String

en	Text

en	Rich text*

en	Integer

en	Floating point

en	Boolean

en	Date time

en	Date*

en	Time*

en	Time/Sec*

en	Select list

en	File*

en	Image*

en	File reference*

en	Folder*

en	Password

en	Is required?

en	Relations

en	Name

en	The name should be lowerCamelCase and unique in this model

en	Extension properties

en	Tab label

en	Lazy loading

en	Make this relation lazy loading

en	Relation to external class

en	If this is a relation to an external model, enter the (full qualified) class name here. The class must exist and be loadable