Bug #17276
closed
Foreign_selector +foreign_unique on click issue
0%
Description
Setting foreign_selector and foreign_unique to same field makes it impossible to select a certain item from the selector via onClick. The first item of the selector gets added regardless of which was actually clicked.
This issue can be reproduced using the IRRE tutorial extension and
setting:
TCEFORM.tx_irretutorial_mnasym_hotel.offers.config {
foreign_selector = offerid
foreign_unique = offerid
size = 5
}
At the "m:n asymmetric selector" - page
(issue imported from #M5564)
Files
Updated by Nikolas Hagelstein over 17 years ago
The attached patch should solve this issue.
Updated by Oliver Hader over 17 years ago
The patch in file "foreign_unique.diff" just removed the problem for the given situation but didn't solve it.
It is possible to use uniqueness with and without a selector. If used without a selector, newly created children on an intermediate table don't have an information about which record is related - thus the first one of the remaining possibilities is used.
If uniqueness is used with a selector, this information is already given.
The solution is to execute the "set the selected item automatically to the first of the remaining items" party only in the situation that no selector is available.
Updated by Oliver Hader over 17 years ago
- TYPO3_4-1: rev. 2347
- Trunk: rev. 2348