Conflict with ACF Select2 fields

  • Resolved Jay Lehtinen

    (@jaylehtinen)


    3 years, 6 months ago

    This plugin causes the following issue with ACF in the Block Editor: When reordering post items in ACF Select2 field, the new order doesn’t get saved. Console outputs the following error.

    Uncaught TypeError: Cannot read property 'element' of undefined
    at HTMLLIElement.<anonymous> (acf-input.min.js?ver=5.9.7:3)
    at Function.each (jquery.min.js?ver=3.5.1:2)
    at s.fn.init.each (jquery.min.js?ver=3.5.1:2)
    at HTMLUListElement.stop (acf-input.min.js?ver=5.9.7:3)
    at x.<computed>.<computed>._trigger (core.min.js?ver=1.12.1:116)
    at x.<computed>.<computed>._trigger (sortable.min.js?ver=1.12.1:9)
    at x.<computed>.<computed>.x.isFunction.r.<computed> [as _trigger] (core.min.js?ver=1.12.1:116)
    at x.<computed>.<computed>._clear (sortable.min.js?ver=1.12.1:9)
    at x.<computed>.<computed>.x.isFunction.r.<computed> [as _clear] (core.min.js?ver=1.12.1:116)
    at x.<computed>.<computed>._mouseStop (sortable.min.js?ver=1.12.1:9)

    Issue can circumvented by temporarily deactivating Yoast SEO or disabling SEO settings for the post type.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support devnihil

    (@devnihil)

    @jaylehtinen We’re sorry to hear you are experiencing this issue on your site.

    Thank you for bringing this issue to our attention!

    We apologize?for the trouble you are currently experiencing with our plugin. You are actually not the first to report this issue. That means a bug report has been created and is under review by our product team, and this can be viewed here: https://github.com/Yoast/wordpress-seo/issues/17171

    What’s next?
    Our product team will assess the severity of this problem in relation to other open bug reports and new features. Based on their assessment, the bug report will be given a priority level. Our developers work on the highest priority issues first. Unfortunately, this means we cannot give you an estimate of when they’ll start working on your report.

    If you have any further information that may affect the prioritization or help our development team solve this bug, please leave a comment or subscribe to the GitHub report to get updates on the issue.

    Plugin Support devnihil

    (@devnihil)

    We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Conflict with ACF Select2 fields’ is closed to new replies.