FluidTYPO3 / flux

TYPO3 extension Flux: Dynamic Fluid FlexForms
https://fluidtypo3.org
145 stars 214 forks source link

Problem with flux:field.inline.fal when open a inline record panel in TYPO3 7.6 #1033

Closed monosize closed 9 years ago

monosize commented 9 years ago

Working with patch https://review.typo3.org/#/c/44914/.

if you try to open an inline fal record panel, then the content is not correctly loaded via ajax.

Not OK: Using <flux:field.inline.fal .../>

image

OK: standard image element with link, description and cropping

image


what I found out is...

image

image

the parent flexform configuration is not created.

The only known value is the uid of the tt_content record in the databaseRow array. We need a dataProvider that can create the data based on the uid of the tt_content table. The dataProvider must verify, that the record is a fluid content element.

@NamelessCoder: Is there such a function in the flux cosmos, that we can use?

julianxhokaxhiu commented 9 years ago

+1 having the same issue here on 7.6 LTS

Damn, what's wrong with T3 main Devs?

For now resolved by cherry picking the patch.

cedricziel commented 9 years ago

Calm down.

NamelessCoder commented 9 years ago

Omelet, eggs @julianxhokaxhiu ;)

julianxhokaxhiu commented 9 years ago

Btw with that patch anyway is not working. I though that would be the fix but it's not. Any suggestion rather than eggs to me? :P

NamelessCoder commented 9 years ago

@julianxhokaxhiu I do :)

Follow https://github.com/FluidTYPO3/flux/issues/1013 and https://review.typo3.org/#/c/44914/. The former is this same issue, already reported, but with a lot more information attached (so I will close this issue and keep the other open). The latter is the first of what I expect will be two or three patches total which fix the regression in TYPO3 itself. First to actually trigger the parent config resolving, second to retrieve the $row from database when it only contains a UID.

monosize commented 8 years ago

Problem is resolved with commit TYPO3/TYPO3.CMS@e6727c8e9ae4cb912bc2d59c79758fb32370641c