Viewing 1 replies (of 1 total)
  • Hi @benny54,

    ACF Support Team here.

    Thank you for reporting this and providing the exact file paths! It looks like there is a specific script conflict happening here between ACF and Divi’s Visual Builder.

    When ACF initializes its WYSIWYG fields, it calls on the core WordPress TinyMCE scripts. It appears Divi 5 is overriding the default TinyMCE base URL to point to its own bundled assets, which inadvertently causes WordPress to look for the native wptextpattern script inside the Divi directory where it does not exist under that exact folder name.

    Because this involves how Divi explicitly routes its builder assets alongside our editor initialization, our team will need to investigate this closely to implement a possible compatibility patch. Could you please open a bug report ticket at https://www.advancedcustomfields.com/contact/ with these details? That will allow us to safely test this exact environment, log the issue for our engineers, and keep you updated on a fix!

    Best regards,
    Patroba

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.