flux compatibillity

[aarree]

Hi, I have a clean T3 8.7.7 installation with flux, fluidpages, vhs etc. ... running. I'am trying to get Frontend editing to work with my custom Flux CE's. How can i access the flux xml fields with the core:contentEditable Viewhelper?

[dr-bock]

i think, there is currently no way. but yes, a flux content-element support would be nice :)

[ZweisteinT]

Any news on that? Will it come or not? :)

[MattiasNilsson]

To be honest it have not been looked into, and the priority is very low.

[rupasix]

It's doable with flux9 because of colpos usage but i think it needs lots of overrides on frontend_editing part. We need, atleast after my short analyze:

• viewhelper to pick content by colpos (afaik port $wrapperService->wrapContentWithDropzone() to viewhelper),
• hide dropzones for parent to child relation (to avoid droping parent elements to child),
• allowed/denied logic for d&d,
• Right sidebar - nesting elements in ce list,
• logic when buttons moveup and movedown should be visible and how should it work (right now it uses flat array relations between ce, with flux we have nesting),
• ability to turn off dropzones and d&d for proxy ce (rendered by typoscript or v:content.render etc.)
• Inline editing for flexform fields
• ???

I've tried to do something but i realized that it needs a lot of time and php + extbase knowledge and i have none. Still, if someone tries to write some kind of frontend_editing > flux connector, i can help with JS/frontend part.

[ZweisteinT]

In my opinion not everything of frontend_editing is needed. For a lot of people, including me, you have your finished layouts and pages, but it would be nice to edit the texts and maybe Images on frontend only.

[rupasix]

Do you mean inline editing right? Because editing in modal (access by editicons) should work just fine with ts lib.contentElement.stdWrap.editIcons = tt_content:header.

[MattiasNilsson]

@rupasix Can you confirm that it works with lib.contentElement.stdWrap.editIcons = tt_content:header?