wysiwyg init on flexible content fields

  • Resolved jabbadu

    (@jabbadu)


    3 years, 5 months ago

    Hi,

    on a custom page i’ve got an issue with the wysiwyg editor inside flexible content fields.

    the backend is highly customized, but the integration with acfe worked nearly perfect.
    most of the issues i could fixed but all the wysiwyg editors are not clickable if there is no content (visual editor). i dont use any acfe flexible content advanced settings on that field.

    There is a js-file ‘acfe-field-group.js’ and on line 190 there is an acf-action show_field/?type=wysiwyg. if i comment this line out, all wysiwyg fields are working.

    is there a possiblity, to override this action via theme so i dont have to modify the acfe plugin-file?

    thanks in advanced
    if you need further information just let me know

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Konrad Chmielewski

    (@hwk-fr)

    Hello,

    Thanks for the feedback!

    I think you’re talking about the file acfe-input.js:190. This code is a builtin ACF Extended feature which enhance the page loading speed when the page has many WYSIWYG fields in different Flexible Content Layouts.

    The WYSIWYG fields in layouts are all set to “Delay Init” and are automatically initialized when a layout is opened by the user or opened by default. In your case, the browser doesn’t understand it has to initialize the WYSIWYG (if I understood correctly your report).

    It seems like you have some compatibility issues or maybe a custom code somewhere which break the native ACF JS code that manage opened/closed layouts.

    Can you try to open your browser console, reload the admin page and check if there is any JS error?

    In order to check if there is a compatibility issue with an another plugin, can you please try to disable all plugins (at the exception of ACF/ACFE) and switch back to the native WP Twenty Twenty One theme?

    You can use the excellent Duplicator plugin if you prefer to clone your website and test those changes on a local environment.

    Sorry for the inconvenience.

    Regards.

    Plugin Author Konrad Chmielewski

    (@hwk-fr)

    Hello,

    Any news?

    Regards.

    Thread Starter jabbadu

    (@jabbadu)

    Hey!

    Yeah, i managed to solve this issue. your hint with the delay was the right way. We had some custom code wich collided. Thanks for that!

    I am sure you can help me with some other little problems. I will open separate tickets for that.

    Regards

    Plugin Author Konrad Chmielewski

    (@hwk-fr)

    Hello,

    I’m glad to hear it now works as expected ??

    Have a nice day!

    Regards.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘wysiwyg init on flexible content fields’ is closed to new replies.