Closed witrin closed 10 years ago
The second problem is already reported at #478. Sorry!
@NamelessCoder You have closed #478 with the reason it's already reported in #431. But I think #431 targets only the first problem here, which is not that bad (your suggesting using something like if
). But it doesn't targets the second problem that all FAL fields in several object having the same values after saving, which makes it useless. Anyway you wrote further this should be fixed by https://review.typo3.org/#/c/30633/. But unfortunately it is not. I've tested the mentioned case above with TYPO3 CMS 6.2.4 and the issues still exist. Did I miss something here?
To make the second problem with TYPO3 CMS 6.2.4 more clear:
Ok now I found the right issue #468. Sorry to bother you all here. Unfortunately currently I'm not able to contribute or sponsor the feature (https://github.com/FluidTYPO3/flux/tree/workbench/relationsettings). So I'll wait. Thanks!
I hope this is not already reported or known. I can't find any related anyhow.
I'm using latest development from
vhs
,flux
andfluidcontent
with TYPO3 6.2.3 and the following template:I'm facing two problems with this configuration:
item
there is only the buttonCreate new relation
for the fieldimage
visible. When use this button to add an image or file I getWrong configuration in <hash>
(e.g. hash = 2ab65...) and the file isn't added. But when I have saved the objectitem
without an image or file the second buttonSelect & upload files
appears and I'm able to add a file without any problems.item
object itsimage
field is always identical with the first one an vice versa. So a can't have differentimage
fields for differentitem
objects.