Bug #29122

Epic #62041: twbs Bootstrap backend, refactor EXT:t3skin and HTML5 output

Epic #62836: FormEngine PHP/HTML Improvements & Bootstrap

TCA renderMode "Tree" issue with multi-relation or MM

Added by Gabriel Kaufmann / Typoworx NewMedia almost 9 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
FormEngine aka TCEforms
Target version:
-
Start date:
2011-08-19
Due date:
% Done:

0%

TYPO3 Version:
4.5
PHP Version:
Tags:
Complexity:
medium
Is Regression:
No
Sprint Focus:

Description

I tried the new renderMode "tree" feature for use in TCA. I got it working with a very simple relation in one of my projects. I would need to use a MM-Relation, but this doesn't work correctly.

Is this feature correctly implemented yet? How do I have to enter the option for the tables used?

Let's imagine we would need a Tree for tt_address tables:

- tt_address_group => tt_address_group_mm -> tt_address

How would the code for it look if it is implemented yet for working? I didn't figure it out how to do it right.

History

#1 Updated by Ingmar Schlecht almost 9 years ago

  • Assignee set to Steffen Kamper

@SteffenK: Could you have a look at this issue? I think you implemented the tree feature, right?

#2 Updated by Gabriel Kaufmann / Typoworx NewMedia almost 9 years ago

Ingmar Schlecht wrote:

@SteffenK: Could you have a look at this issue? I think you implemented the tree feature, right?

Hello Ingmar,

I hope I tried it right. I successfully used the tree in some of my extensions without using mm-relations. Those worked fine.

I tried to adpot the following example snipplet for mm-relations. But all I got was the tt_address Group-Title. I also tried to modify it in some ways to set the "tt_address_group" table in the tca-config - or is this unnessecary as it will be resolved using the mm-table by TCA-processing?

TCA Definition

'config' => array (
    'type' => 'select',
    'internal_type' => 'db',
    'size' => 20,
    'minitems' => 0,
    'maxitems' => 999,
    'foreign_table' => 'tt_address',
    'foreign_table_where' => 'ORDER BY tt_address.uid',
    'MM' => 'tt_address_group_mm',
    'renderMode' => 'tree',
    'treeConfig' => array(
//     'rootUid' => 214,
        'parentField' => 'pid',
        'appearance' => array(
            'expandAll' => TRUE,
            'showHeader' => TRUE,
            'maxLevels' => 2,
        )
    ),
),

This is what I expected to get:

[Tree Root]
 |
 [+]_tt_Address_Group "Group A" 
 |   |
 |   |_ tt_Address A in Group A
 |   |_ tt_Address B in Group A
 |
 [+]_tt_Address_Group "Group B" 
 |   |_ tt_Address C in Group B
 |   |_ tt_Address D in Group B
[..]

I am right that this should be working? This is what I would expect on a tree using MM-Relation.

Best regards
Gabriel

#3 Updated by Andreas Wolf over 8 years ago

  • Category set to FormEngine aka TCEforms
  • Complexity set to medium

#4 Updated by Xavier Perseguers over 8 years ago

  • Assignee deleted (Steffen Kamper)

#5 Updated by Thomas Deinhamer over 7 years ago

Seems like this is not working with MM-tables yet.

#6 Updated by Gabriel Kaufmann / Typoworx NewMedia almost 7 years ago

Is there something new on this?

I think a tree-function like this makes really sense. But making it usable with one table only (without table relations) makes it usable only in some basic terms.

#7 Updated by Jigal van Hemert almost 7 years ago

  • Status changed from New to Needs Feedback

It does work with MM-relations, but not through a chain of relations like in your example.

The select field of internal type 'db' will make links between your record and the foreign_table via the mm-table. If this is for example a category then it is likely that the records in the foreign_table have a relationship amongst themselves: a parent-child relation. This is where the renderMode 'tree' becomes useful. Via the property 'parentField' you can set the field name that links one record of the foreign_table to its parent (in the same table). Instead of seeing a long list of category names you get a nice tree where it's easier to find the item you want to select.

The select field of internal type 'db' will also not work with your configuration without the renderMode 'tree'.

#8 Updated by Gabriel Kaufmann / Typoworx NewMedia almost 7 years ago

Jigal van Hemert wrote:

It does work with MM-relations, but not through a chain of relations like in your example.

Well does this simply mean it does completly not work and is not planned to be working?
Or is there something I can improve on my current configuration to make it work?

I tried nearly everything but as already told didn't get it work like shown as example above.

#9 Updated by Alexander Opitz over 6 years ago

  • Status changed from Needs Feedback to New
  • Is Regression set to No

#10 Updated by Felix Kopp over 5 years ago

  • Parent task set to #62836

#11 Updated by Riccardo De Contardi over 2 years ago

  • Status changed from New to Needs Feedback

Is it still an issue after the formengine has been rewritten?

#12 Updated by Riccardo De Contardi over 2 years ago

  • Status changed from Needs Feedback to Closed

90 days without feedback -> closing it.

If you think that this is the wrong decision or experience the issue again or have more information about how to reproduce it on recent TYPO3 versions like 8.7.x or 9.0.0, please reopen it or open a new issue with a reference to this one.

Thank you.

Also available in: Atom PDF