About Version 2.x

Here is the meta issue that was created when 2.x was only an idea https://www.drupal.org/project/frontend_editing/issues/3436684 🌱 [Meta] Plans for 2.x Active . It explains what benefits are there when using extra field.

More over extra field settings allow to choose what form display you want to use in Frontend Editing sidebar. In 1.x it is only "Default" form mode, in 2.x you can choose yourself.

Thank you @a.dmitriiev,

I had a vague memory that I had seen this somewhere before.

Very nice feature additions!

I have just noticed that since the update to 2.x, I have lost:
1) The UP/DOWN buttons and
2) The ability to add new Paragraphs above and below.

I kind of expected that I might have to go over to the form disapply and choose which options I want 'though I would have expected them ALL to ON by default but it's worse than that as I can see the place where I am supposed to be able to click the various toggles ON and OFF as shown in your proposal screenshot but they are not there ...

?

The move up and down and add new items buttons are the settings from the entity reference field, where your paragraph (for example) leaves. As this functionality is connected to the field itself, not to the entity. So if your paragraph is inside the node of type "Page" field called "Paragraphs", then you need to go to "Manage display" of "Page" content type, find "Paragraphs" field and click the settings button, there you will see the ON/OFF toggles for move up/down and add new items.

Actually, that was indeed my expectation but I was led instinctively to the Frontend Editing Editing Actions form component probably because of its name.

Perhaps it should be called 'Front end editing FORM MODE' instead?

I'm all sorted now though, the toggles are all there after all ;-)

The component "Frontend Editing: Actions" on "Manage display" is actually still needed, because if you move it to "Disabled" section, then no frontend editing actions will be available for this view display anymore. This element is more for you to decide whether you need the element or not. Let's say you have paragraph in view mode "Only label" and another one "Default". For "Only label" you don't want to have a frontend editing, as it would be clumsy. So for this view display you just need to drag the element to "Disabled" and it will not be shown anymore, but for "Default" it will still be there. This is on of the differences between version 1.x and 2.x, that it is possible to control in UI for what view modes one wants to display frontend editing actions, because in version 1.x it was only possible with module hooks.

Got, thank you.