- Issue created by @kumkum29
- π©πͺGermany breidert
I suspect it is related to your twig templates. Please try to switch to Olivero theme and check if you can reproduce the error there as well.
- π«π·France kumkum29
@breidert, I have tested on several theme the 'frontend editing' module.
Claro > OK
Olivero > OK
Gin > OK
Radix base > OK
My subtheme on Radix > KOThe problem seems to be with my custom theme (On Radix) and how I include elements in templates. With the 1.1.1 version I haven't see this problem.
So I'm looking to modify the rendering of the entities in my tpls...
Thanks.
- πΊπΈUnited States kurttrowbridge
In case it helps, I had this problem as well, but resolved it by ensuring my node template had the
{{ content }}
variable in it. (I had been more specific, with variables like{{ content.body }}
, but I swapped it out in favor of{{ content|without('fields_I_did_not_want') }}
.) - π©πͺGermany a.dmitriiev
@kumkum29 1.x-dev version changed the rendering of the action links. Before javascript was responsible for this, now the links should be rendered from twig. The element is called
frontend_editing
, so in your template there should be a place somewhere with{{ content.frontend_editing }}
. The reason why it was done in this way is the number of new actions that were added. Frontend editing is not anymore change "Edit" button. For paragraphs you can now change the order of them and add new paragraph before or after the given paragraph. These new actions require more access checks and also rendering 5 links in javascript is not the best approach.So, just make sure that somewhere in the template you have
{{ content.frontend_editing }}
(the same as for contextual links) and also make sure that settings here/admin/config/frontend-editing/entity-bundle-restrictions
allow using frontend editing with given entity type and bundles.I hope this comment clarifies the idea of a new version.
- Status changed to Closed: works as designed
about 1 year ago 3:41pm 12 October 2023 - π©πͺGermany a.dmitriiev
I have added this information to the project page, so closing this issue.