EXT: Zentigrator¶

Table of Contents¶

EXT: Zentigrator 1

`Introduction 3 <#__RefHeading__2400_547203128>`_

What does it do? 3

Screenshots 3

Here are some screenshots of the plugin running a well-known Zend Framework tutorial programm. 3

`Users manual 4 <#__RefHeading__2408_547203128>`_

FAQ 4

`Administration 5 <#__RefHeading__2412_547203128>`_

FAQ 5

`Configuration 6 <#__RefHeading__2416_547203128>`_

FAQ 6

Reference 6

`Tutorial 7 <#__RefHeading__2422_547203128>`_

`Insert the plugin. 7 <#__RefHeading__2424_547203128>`_

`Make your Zend application available to TYPO3. 7 <#__RefHeading__2426_547203128>`_

`Make all resources of the Zend application available for Browsers (put it into fileadmin/). 7 <#__RefHeading__2428_547203128>`_

`Configure the plugin as described above. 7 <#__RefHeading__2430_547203128>`_

`Enjoy. 7 <#__RefHeading__2432_547203128>`_

`Known problems 8 <#__RefHeading__2434_547203128>`_

`To-Do list 9 <#__RefHeading__2436_547203128>`_

`ChangeLog 10 <#__RefHeading__2438_547203128>`_

Introduction¶

Users manual¶

Simple add the plugin to your page and give the path to a Zend Application you want to embed. Note that the Zend Application has to have an application/configs/application.ini file for configuration. Within this file configuration sections must be defined. In your plugin setup, give one of those section names in the environment field.

The plugin assumes a Zend application configuration file called application.ini in <Path2YourZendApp>application/config/ folder. This is common to a structure created by the the zf tool. In order find the application, the plugin must know where the application lives. Therefore a parameter zend.application.path has to be specified in the TypoScript setup template. Zend application config files usally define different configuration sections like testing, development or production. You will have to choose one of those in zend.application.environment to tell plugin and application what mode to run at.

Here is an sample configuration snippet:

[production]
phpSettings.display_startup_errors = 0
phpSettings.display_errors = 0
phpSettings.date.timezone = "Europe/London"
includePaths.library = APPLICATION_PATH "/../library"
bootstrap.path = APPLICATION_PATH "/Bootstrap.php"
bootstrap.class = "Bootstrap"
appnamespace = "Application"
resources.frontController.controllerDirectory = APPLICATION_PATH "/controllers"
resources.frontController.params.displayExceptions = 0
resources.db.adapter = PDO_MYSQL
resources.db.params.host = localhost
resources.db.params.username = rob
resources.db.params.password = 123456
resources.db.params.dbname = zftutorial
resources.layout.layoutPath = APPLICATION_PATH "/layouts/scripts/"
resources.view.doctype = "XHTML1_STRICT"


[staging : production]

[testing : production]
phpSettings.display_startup_errors = 1
phpSettings.display_errors = 1

[development : production]
phpSettings.display_startup_errors = 1
phpSettings.display_errors = 1
resources.frontController.params.displayExceptions = 1

|img-5|
}

Administration¶

On installation, specify the path to a Zend Framework 1.10.6 distribution:

Configuration¶

In order to run the Zend application a copy of ZendFramework 1.10.6 (or higher) has to be available in the include path or it has to be found in the extensions lib/ folder. A common way is to create a symbolic link to the library/Zend/ folder of your framework distribution. It's crucial that no other Zend Framework version has been made available to system before execution of the plugin.

Tutorial¶

• Insert the plugin.
• Make your Zend application available to TYPO3.
• Make all resources of the Zend application available for Browsers (put it into fileadmin/).
• Configure the plugin as described above.
• Enjoy.

Known problems¶

• Yet, the extension is beta.
• Forms shall not contain fields called like TYPO3 reserved fields. For example: id, no_cache etc. So an application has to be altered for this sake. When submitted as post data, those fields will override the TYPO3 parameters. In further versions a special post-data-hook might solve this problem by dispatching post parameters.
• TYPO3 Forge link to Zentigrator

To-Do list¶

• Add hook to dispatch reserved TYPO3 parameter names from HTTP posts.
• TYPO3 Forge link to Zentigrator

ChangeLog¶

• Create a file "ChangeLog" (see e.g. the extension "cal" as example) to inform about changes or
• Use this section to document all the changes through the versions.
• Alternative to the following list: ChangeLog online (point this link to YOUR extension)