Bug #31637
closedUnselectable items with renderMode=tree
100%
Description
In Short: Using a select with renderMode=tree in TCA and maxitems=1 can become impossible when the referenced entry gets deleted.
I have a database table which contains a select with renderMode=tree, which references the pages table. You can select exactly one page):
'page' => array( 'exclude' => 0, 'label' => 'Page', 'config' => array( 'type' => 'select', 'foreign_table' => 'pages', 'foreign_table_where' => 'ORDER BY sorting ASC', 'minitems' => 1, 'maxitems' => 1, 'renderMode' => 'tree', 'treeConfig' => array( 'parentField' => 'pid', 'appearance' => array( 'expandAll' => false, 'maxLevels' => 999, ), ), ), ),
The page tree is rendered beautiful and I like this new feature :)
I ignored the bad usability with maxitems 1: When one item is selected, you can't click on another item to select it. You have to unselect the selected item first.
But this exact usability defect leads to the bug, that you cannot select anything:
- Select a page, save the record
- Go to the page tree and delete the page
- Come back to the record and try to select another page
It's impossible to select another page, because the widget has remembered, that it already has a page selected and that you have to unselect it first. This is now impossible because the page does not appear in the tree and the widget is completly unusable.
Updated by Benni Mack almost 13 years ago
Could it be that this is a duplicate of #20422 as this phenomena is similar to all existing selects...
Updated by Benni Mack almost 13 years ago
- Category set to Backend User Interface
- Status changed from New to Accepted
Updated by Robert Vock almost 13 years ago
Benjamin Mack wrote:
Could it be that this is a duplicate of #20422 as this phenomena is similar to all existing selects...
It's possible that it is the same, but I am not sure. I don't know if the bug exists in the JavaScript for the tree (and the Element browser again) or if it is shared code between those two widgets.
But it would be a good usability upgrade to make it possible to automatically unselect items when maxitems=1 and you click on an item.
Updated by Nicolas Forgeot over 11 years ago
It's bug persists in 6.0.x / 6.1.beta, when entry is deleted or hidden.
Updated by Alexander Bigga about 10 years ago
This issue persist in recent 4.7.19, 6.1.9 and 6.2.3 :-(
Updated by Gerrit Code Review about 10 years ago
- Status changed from Accepted to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/31171
Updated by Gerrit Code Review about 10 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/31171
Updated by Gerrit Code Review about 10 years ago
Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/31480
Updated by Gerrit Code Review about 10 years ago
Patch set 1 for branch TYPO3_6-1 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/31481
Updated by Anonymous about 10 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 10b853dc9a312103afd5902e91f1c82ed0cc3860.
Updated by Benni Mack almost 6 years ago
- Status changed from Resolved to Closed