[BUG] Flexform variable population failing on TYPO3 4.7.7 with current Version Utility about flux HOT 3 CLOSED

Hi Tommy,

Since I'm lacking a test environment for this specific thing, would you mind testing this suggested fix:

/**
 * check for versions of TYPO3 which do not consistently pass $fieldName
 *
 * @return boolean
 */
public static function assertHasFixedFlexFormFieldNamePassing() {
    return self::assertCoreVersionIsAtLeastSixPointZero();
}

I believe it's a better solution, given that the bugfix that is supposed to fix this field name passing most likely will not be fixed anytime soon (and once it is fixed, the proper versions which fixes it will be known).

Cheers,
Claus

from flux.

Hi Claus,

thanks for your feedback & your fix proposal. I think this fix is not necessary now, as 4.7.8 is available since some days.

Can you please close this issue because fetching of field values from the page flexform is working now.

As a side note I'd like to add that in 4.7.8 the frontend will throw an exception if a dynamic layout name ("{settings.layout}") is in use and the flexform field is named like "settings.myFancySetting".

Blessings,

tommy

from flux.

Hi Tommy,

Actually there is still an issue in the core which is not fixed: https://review.typo3.org/#/c/16022/ pending for quite a while now and it doesn't look like it will be part of 4.7.8 either. The sad thing is that the field name is passed in some cases and not in others, which means that in 4.x there's no other choice currently than to assume the field name is not passed. You are most certainly welcome to push for merging the TYPO3 core change but I'm afraid I am out of patience with the core review process.

The good news is that on 6.0+ this has been fixed completely. By simply replacing a core class.

I'll include the patch and wait for whenever somebody decides to merge the nobrainer commit which changes a single line in the core...

Cheers,
Claus

from flux.