Sebastian Helzle
Sebastian Helzle
### Description When having an inline editable text that is also editable via the RichtTextEditor in the inspector, opening the secondary editor will show an additional toolbar to the one...
### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior I have to run `./flow flow:cache:flushone Neos_Fusion_ParsePartials` when changing something in...
Given I have an image with the dimensions 2000 x 700 Now my (reduced) implementation is as follows: ``` ``` Now the output of the sources is limited to 1050...
For example a preset called `My.Vendor:Preset.Carousel` would not be found as `getValueByPath` in `applyPreset` does an explode on `.`. This is confusing as the documentation of Neos advices to use...
This is implemented the same way as in the `Flowpack.ElasticSearch.ContentRepositoryAdaptor` with the same setting.
Pros: * Full API access and data only has to be loaded once * Better Neos UI integration * Get rid of some legacy code from before React UI times...
Currently the text will just revert on save when it's too long.
This can be done with https://shields.io/category/platform-support, but it might be necessary to move the package.json into the root folder.
Currently the editable fields are rendered hidden and are filled by the Snippet Editor after changes occur. Instead it would make sense if the Snippet Editor is an actual Neos...