Functional only on media entities

Created on 29 August 2023, 10 months ago
Updated 12 October 2023, 9 months ago

It is a fabulous and promising module to improve content editing !

Unlike version 1.1, the DEV 1.0 version only works on media entities.

If I hover over an entity paragraph, content or taxonomy term, no hover link appears.

If I analyze the html code of the page, the div including the links (.frontend-editing-actions) is only present on the media elements.

However, in the admin I have selected the following entities: paragraph, content and taxonomy.

I cleared the cache several times and closed my session several times without success.

I did not find any error in the site logs.

Thanks for your replies.

πŸ› Bug report
Status

Closed: works as designed

Version

1.0

Component

Code

Created by

πŸ‡«πŸ‡·France kumkum29

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • 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 > KO

    The 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 9 months ago
  • πŸ‡©πŸ‡ͺGermany a.dmitriiev

    I have added this information to the project page, so closing this issue.

Production build 0.69.0 2024