Claus Due

Either: * Pass a properly configured `FileReference` or `File` with crop definition as `src`; alternatively, define crop behavior in TS . * Or pre-process the input for `src` with `f:uri.image`...

For current projects you are strongly encouraged to use just Flux and avoid Fluidcontent. With a tiny bit of migration you can convert old projects to Flux only - and...

Not to dismiss the problem, but: you should not be using `f:translate` within Configuration sections - ideally you should rely on the automatic building of field labels, or use full...

Sounds like a problem with the JS or CSS that gets loaded (or rather should get loaded) when editing inline, but not when editing in the normal way.

This changes the TYPO3 compatibility of the extension and shouldn't enable strict types or declare strict returns. AFAIK it is possible to have compatible signatures for both v9 and v8...

Can you explain a bit which exceptions and in which context you are seeing them? The `v:render.uncache` ViewHelper has been tested and confirmed working on TYPO3v10, v11 and v12.

Both `f:image` and `f:form.*` are specific to TYPO3 CMS and will not work in Fluid standalone - you would need to emulate these ViewHelpers, e.g. create an emulated `f:image` that...

Hi @kaesetoast - the reason for using `.fluid` is simply the way PatternLab works. Initially I tried developing it to use `.html` but this has some rather unfortunate side effects,...

I concur: please create at least one stable tag for this, as well as a branch alias. Currently facing issues trying to use the package in `--dev` of another package...

As far as I can see those are the correct allowed types according to your setup. Could you explain what you expect as a result?