Claus Due

@paul-siteway I doubt there's anything I could do about this problem. Gridelements works by overriding the `colPos` value of content within its content areas, setting it to `-99`. Flux works...

@Bunnyfield Flux doesn't actually do any assigning of colPos values as such. Instead, it uses the core's functionality to render a standard content area with a special colPos. The colPos...

@Bunnyfield I'm just shooting from the hip here, but could the problem be that Gridelements JS is triggering and/or assigning a drop event listener _recursively_ on every content drop-zone within...

I doubt that `renderType` is the reason for this. It more seems like TYPO3 is now capable of passing a FlexForm identifier array which does not contain the `type` attribute....

Hi @Zellwerker, Just a quick note for now: this code block was deactivated because it caused problems with other copy operations. Unfortunately, TYPO3 chose to use the `copy` command instead...

There should be no negative effects in connected mode, since IIRC the command then changes to `copyToLanguage` which of course doesn't trigger this block. It's only free mode that causes...

Hi @afle, Are you by any chance calling this ViewHelper in a backend context? If so, that is not supported and would explain the problem. If you are using it...

The underlying cause is that content object data resolving has become very inconsistent since storing TSFE and cObj within the Request attributes, as well as delivering those objects through various...

This ViewHelper is explicitly designed to only render output if the content is exactly `null` (implied: variable is undefined). It should not be comparing to anything other than explicitly `null`;...

See https://github.com/TYPO3/Fluid/pull/396 (would allow array union with `+` operator in variable accessor syntax). IMHO, it should not be allowed to modify properties of already-assigned variables. It's fine to _replace_ the...