[TYPO3-mvc] Correct mapping of tables and fields via Typoscript

[Thomas "Thasmo" Deinhamer]

Thanks a lot for your information.

Some days ago I also tried to reorganize some TS
inside my new extbase extensions, and wondered, that
this is not working:

plugin.tx_myext_pluginname {
	settings {
		
	}
}

Unfortunately the defined settings won't be available
inside the controller of the desired frontend plugin.

This works:

plugin.tx_myext {
	settings {
		
	}
}

Wondering if it is possible to somehow have a better
solution for structuring a lot of TS; imho the first
snippet above would be cool to use.

Is this possible?

Thanks,
Thomas


Am 03.02.2010 12:00, schrieb Jochen Rau:
> Hi Thomas,
>
> On 29.01.10 23:55, Thomas "Thasmo" Deinhamer wrote:
>> Good evening,
>> sorry for spamming the list with new topics,
>> but a lot of questions came up the past week.
>>
>> For now I do map special named classes or fields
>> like this:
>>
>> config.tx_extbase {
>> persistence {
>> classes {
>> Tx_EXT_Domain_Model_Object {
>> mapping {
>> tableName = table
>>
>> columns {
>> tx_ext_field.mapOnProperty = field
>> }
>> }
>>
>> columns {
>> field.foreignClass = Tx_Ext_Domain_Model_Object
>> }
>> }
>> }
>> }
>> }
>>
>> Is this the correct way? I'm wondering if the nesting is okay?
>> Also is it better to defined the mapping inside the extension itself,
>> like:
>>
>> plugin.tx_ext {
>> persistence {
>> ...
>> }
>> }
>
> The lines
>
> columns {
> field.foreignClass = Tx_Ext_Domain_Model_Object
> }
>
> are obsolete and not properly nested neither.
>
> plugin.tx_ext {
> persistence{...}
> }
>
> should also work. Please report an issue if not.
>
> Jochen