Hint on how to use Select2 within "ACF guidelines" about acf-field-type-template

[elliotcondon]

Hi @hbi99

Thanks for the question, but I don't understand.

Please review the Select2 examples here:
http://ivaynberg.github.io/select2/

[hbi99]

Yeah...but it seems that you are using an old version in ACF and it can be updated without breaking ACF. Ah well...I'll solve it anyway

[elliotcondon]

Hi @hbi99

You can register your own select2 library if you wish.
ACF will use any library that is registered before the enqueue_scripts action

[hbi99]

@elliotcondon,
Are we talking about the same thing? When javascript is getting evaluated, your old-version registers itself as plugin to jQuery. When my new version is loaded, it is not registered or extends the old version.

Please do not guess or suggest if you are not sure that your suggestion actually works.
Why don't you update this repo with the new version of Select2 instead?

[elliotcondon]

Hi @hbi99

ACF PRO will register the select2 library during an action called ''acf/input/admin_enqueue_scripts". This is a custom action that is run during the WP action "admin_enqueue_scripts" with a priority of 20.

If you hook into the "init" or "admin_enqueue_scripts" actions with a priority less than 20 (10 would be safe), you can use the wp_register_script() and wp_enqueue_script() functions.

You can see how ACF PRO registers the select2 library in the acf/fields/select.php file.

ACF uses select2 v3 due to limitations in select2 v4.
I have added compatibility with v4, but I am not adding it to my plugin until Select2 address the issues with sort-ability.

Please do not insinuate that I am 'guessing' or not attempting to help.
I am helping you for free and would appreciate your co-operation in solving your issue, not complaining.