Claus Due

The wrapper was removed since for quite some time, FormEngine has not required it to be present. This leaves just one place - the callback handling in FlexFormTools, which as...

Hi @dogawaf - I appreciate the patch but I'm inclined to reject it. The type-specific fields have been deprecated in favor of `flux:field` which can be used universally to create...

> For this very reason I would consider this a bug that should be fixed in the current versions of flux. That's reasonable enough, even if the text-specific field feature...

I'll give you some ideas about solving / working around this problem and then try to answer the many questions that came up. First you have to know how the...

Flux, like any other TYPO3 extension using Extbase's ConfigurationManager, is affected by limitations of the ConfigurationManager when reading TypoScript. See https://github.com/FluidTYPO3/flux/issues/1671 for a more detailed explanation.

Class loading may be incorrectly configured, your PageController's namespace may be incorrect (case sensitivity may apply) or there may be a typo in the class name or file. You should...

I think this problem was solved with commit https://github.com/FluidTYPO3/flux/commit/19279684f1792f373d3a1fafdbde4dea0e4e12d9 (currently only in the `development` branch) - but it would be great if you could confirm! Side note: if you need...

@X-Tender have you tried this with `dev-development` of Flux? There should be no difference in terms of inheritance between normal fields and section objects...

> This would break the `undelete` command in DataHandlerSubscriber (triggered when you restore an element from Recycler). The method `getSingleRecordWithoutRestrictions` was intentionally introduced to allow loading records completely without restrictions,...

Don't merge - I will take care of this one manually. It has relations to our `fluidtypo3-development` package and the manipulation of the composer class loader should instead be depended...