Support

Account

Home Forums ACF PRO ACF Pro select2 incompatibility with ProfilePress

Helping

ACF Pro select2 incompatibility with ProfilePress

  • Have a client who’s WordPress site automatically updated to ACF Pro 11.5.3. This site is heavily reliant on ACF fields and blocks.

    This caused a select2 Javascript crash while editing pages containing ACF blocks, resulting in some blocks missing with Your site doesn't include support for the "acf/hero-" block. You can leave this block intact or remove it entirely.

    The dash is interesting in the block ID there because I don’t believe we have a dash in the actual block ID. But each missing block has a dash like that.

    Here’s the stack trace:

    Uncaught Error: No select2/compat/dropdownCss
        D https://***/wp-content/plugins/wp-user-avatar/assets/select2/select2.min.js?ver=5.8.2:2
        s https://***/wp-content/plugins/wp-user-avatar/assets/select2/select2.min.js?ver=5.8.2:2
        e https://***/wp-content/plugins/wp-user-avatar/assets/select2/select2.min.js?ver=5.8.2:2
        apply https://***/wp-content/plugins/wp-user-avatar/assets/select2/select2.min.js?ver=5.8.2:2
        e https://***/wp-content/plugins/wp-user-avatar/assets/select2/select2.min.js?ver=5.8.2:2
        d https://***/wp-content/plugins/wp-user-avatar/assets/select2/select2.min.js?ver=5.8.2:2
        select2 https://***/wp-content/plugins/wp-user-avatar/assets/select2/select2.min.js?ver=5.8.2:2
        jQuery 2
        select2 https://***/wp-content/plugins/wp-user-avatar/assets/select2/select2.min.js?ver=5.8.2:2
        initialize https://***/wp-content/plugins/advanced-custom-fields-pro/assets/build/js/acf-input.min.js?ver=5.11.3:1
        e https://***/wp-content/plugins/advanced-custom-fields-pro/assets/build/js/acf.min.js?ver=5.11.3:1
        Model https://***/wp-content/plugins/advanced-custom-fields-pro/assets/build/js/acf.min.js?ver=5.11.3:1
        n https://***/wp-content/plugins/advanced-custom-fields-pro/assets/build/js/acf.min.js?ver=5.11.3:1
        n https://***/wp-content/plugins/advanced-custom-fields-pro/assets/build/js/acf.min.js?ver=5.11.3:1
        newSelect2 https://***/wp-content/plugins/advanced-custom-fields-pro/assets/build/js/acf-input.min.js?ver=5.11.3:1
        initialize https://***/wp-content/plugins/advanced-custom-fields-pro/assets/build/js/acf-input.min.js?ver=5.11.3:1
        e https://***/wp-content/plugins/advanced-custom-fields-pro/assets/build/js/acf.min.js?ver=5.11.3:1
        o https://***/wp-content/plugins/advanced-custom-fields-pro/assets/build/js/acf.min.js?ver=5.11.3:1
        doAction https://***/wp-content/plugins/advanced-custom-fields-pro/assets/build/js/acf.min.js?ver=5.11.3:1
        doAction https://***/wp-content/plugins/advanced-custom-fields-pro/assets/build/js/acf.min.js?ver=5.11.3:1
        7806 https://***/wp-content/plugins/advanced-custom-fields-pro/assets/build/js/acf.min.js?ver=5.11.3:1
        setTimeout handler*7806/< https://***/wp-content/plugins/advanced-custom-fields-pro/assets/build/js/acf.min.js?ver=5.11.3:1
        jQuery 9
        7806 https://***/wp-content/plugins/advanced-custom-fields-pro/assets/build/js/acf.min.js?ver=5.11.3:1
        7806 https://***/wp-content/plugins/advanced-custom-fields-pro/assets/build/js/acf.min.js?ver=5.11.3:1
        n https://***/wp-content/plugins/advanced-custom-fields-pro/assets/build/js/acf.min.js?ver=5.11.3:1
        <anonymous> https://***/wp-content/plugins/advanced-custom-fields-pro/assets/build/js/acf.min.js?ver=5.11.3:1
        <anonymous> https://***/wp-content/plugins/advanced-custom-fields-pro/assets/build/js/acf.min.js?ver=5.11.3:1
        <anonymous> https://***/wp-content/plugins/advanced-custom-fields-pro/assets/build/js/acf.min.js?ver=5.11.3:1
    

    In order to resolve we rolled back to version 5.9.5, which is the only other version of ACF Pro I had available.

    Believe this is a conflict with ProfilePress (3.2.4) because that wp-user-avatar in the stacktrace comes from that plugin. I did try the method in functions.php to deregister the select2 script from both ProfilePress and ACF Pro. It did not resolve the issue in either case, though I believe disabling ProfilePress may have resolved the noted Javascript error. However rolling back to the previous ACF Pro version resolved all issues.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.