[TYPO3-mvc] POST/GET vars

Bastian Waidelich bastian at typo3.org
Fri Oct 22 11:23:52 CEST 2010


Dawid Pacholczyk wrote:

Hi Dawid,

> I have 2 last question to get it all.

That's not too much ;)


> What for are sections persistence and view if I can`t get to them ?

I can think of following configuration options:

persistence.storagePid: sets the page id(s) that Extbase uses to look 
for records

persistence.classes: mapping and inheritance configuration (see 
https://svn.typo3.org/TYPO3v4/CoreProjects/MVC/blog_example/trunk/Configuration/TypoScript/setup.txt)

persistence.updateReferenceIndex (boolean): if set TYPO3s reference 
index will be updated upon write access

persistence.enableAutomaticCacheClearing (boolean): if set, the 
TCEMAIN.clearCacheCmd of the storage page is executed when records are 
changed (see 
http://buzz.typo3.org/people/sebastian/article/finetuning-extbase/ and 
http://buzz.typo3.org/people/ron-hall/article/dont-wear-out-the-clear-cache-button/). 
This is very useful and defaults to TRUE.


view.templateRootPath: base path of the templates (defaults to 
"typo3conf/myext/Resources/Private/Templates")

view.partialRootPath: base path of the partials (defaults to 
"typo3conf/myext/Resources/Private/Partials")

view.layoutRootPath: base path of the layouts (defaults to 
"typo3conf/myext/Resources/Private/Layouts")

view.defaultPid: If this is a number, links point to the page with this 
id by default. If the value is "auto" the target page is determined 
automatically



> Can I read somewhere about that ?

Documentation (toghether with proper error handling) is still a weak 
spot of Extbase & Fluid.
But there are some guides and manuals available that might help you: 
http://forge.typo3.org/projects/534/wiki/Documentation

Apart from that the Book from Jochen and Sebastian 
(http://www.amazon.de/Zukunftssichere-TYPO3-Extensions-mit-Extbase-Fluid/dp/3897219654/) 
is a great help - but unfortunately only available in German so far..


> What is pluginname in tx_extensionname_pluginname. What do you mean by that
> ? I used to plugin.tx_extensionname_pi1 in old school ext developing :)

The naming conventions are (taking the blog_example):

Extension key:      blog_example (= $_EXTKEY)
Extension name:     BlogExample (used e.g. in class names)
Plugin name:        MyPlugin
Plugin key:         myplugin (lowercase, no underscores)
Plugin signature:   blogexample_myplugin
ExtensionNamespace: tx_blogexample (used in TS setup)
PluginNamespace:    tx_blogexample_myplugin (used in TS setup and to 
namespace GET/POST vars)


HTH,
Bastian

In your TS setup you refer to


More information about the TYPO3-project-typo3v4mvc mailing list