• Hello, I just wanted to say that it would be great if you could exclude fields from frontend editing. If you use an acf field to (for example) insert a class name into your code, it gets wrapped in contenteditable html and breaks things. I have also had this problem when creating a text field for inserting font awesome icons into content. I realize that this isn’t an issue if you arent logged in, but from a UX standpoint it isn’t great.

    <div class="modal fade" id="<d contenteditable data-postid=" options"="" data-name="lots_repeater_1_lot_id" data-key="field_58fe3f516b974">lot-2-block-1" tabindex="-1"
    Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)
  • May I second this request.

    Kind Regards
    Brad

    Found a work around supplied by @will83 on a different post that works for me
    Added to the field that you do not want editable – works for me.

    
    strip_tags(get_field('MyFieldThatShouldBeNotEditableInFrontEnd'))
    
    • This reply was modified 7 years, 7 months ago by brad1004.
    • This reply was modified 7 years, 7 months ago by brad1004.

    You can use contenteditable=”false” within your div.

    example:

    <div contenteditable="false">
    <p>this is NOT editable</p>
      <div>                  
    <div contenteditable="true">
      <p>this is editable</p>
    </div>
    Thread Starter pierrehooker

    (@pierrehooker)

    @brad1004 can you elaborate on how/where you use that code?

    @samjco your solution seems to only block the ability to edit the content, but any display issues caused by the plugin making the content editable still remain (per my original post). Ideally there would be a way to tell the plugin to not search and wrap the text in contenteditable areas to begin with.

    Also, it would be great if there was a way to exclude page titles from being editable as well.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Feature Request: Ability to exclude fields from frontend editing’ is closed to new replies.