Title: Select2 Error
Last modified: August 31, 2016

---

# Select2 Error

 *  Anonymous User 13711045
 * (@anonymized-13711045)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/select2-error/)
 * Looks like this plugin uses an older version of Select2. I have a membership 
   plugin which uses the newer version, 4. There’s a conflict between the two plugins
   and one of my pages I’m trying to edit throws this error…
 * Uncaught Error: Option ‘ajax’ is not allowed for Select2 when attached to a <
   select> element. – um-select.js:21
 * It would be very helpful if Ultimate Member could upgrade to the newest version
   of Select2.
 * [https://wordpress.org/plugins/ultimate-member/](https://wordpress.org/plugins/ultimate-member/)

Viewing 1 replies (of 1 total)

 *  [runofthemill](https://wordpress.org/support/users/runofthemill/)
 * (@runofthemill)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/select2-error/#post-8156025)
 * Following up with a similar issue:
 * When using ACF Pro and Ultimate Member with WP 4.5.3, there’s a conflict in WP
   Admin.
 * When ACF Pro is disabled, Ultimate Member settings work fine: [https://infinit.io/_/CRR6wqv](https://infinit.io/_/CRR6wqv)
 * When ACF Pro is enabled, the styling changes, and there seems to be an issue 
   with the z-index (although I don’t see any z-index CSS when inspecting the page
   code) as the menus fall behind the rest of the interface: [https://infinit.io/_/eKyhWMT](https://infinit.io/_/eKyhWMT)
 * I reached out to ACF Pro and their support staff was very helpful, and provided
   the following feedback which I’m passing along for the UM devs:
 * >  I’ve done some debugging through the Ultimate Memebr plugin and found that
   > they are including an older version of the plugin ‘3.4.8’ which uses different
   > class-names than the version that ACF is including (newer) ‘3.5.2’.
   > This explains why when ACF PRO is active, the select2 elements are different,
   > and the Ultimate Member CSS is not working as expected.
   > I noticed some code in their enqueue class that checks for the plugin WooCommerce
   > and dequeues the registered Select2 JS/CSS. Perhaps they can do the same for
   > ACF.
   > Even better, they should consider updating the Select2 version to 3.5.2 (same
   > as ACF and WooCommerce) to allow for better compatibility. They should also
   > consider not including the Select2 JS within a compiled um.min.js file to allow
   > for 3rd party plugins to enqueue the ‘select2’ JS/CSS via WP functions

Viewing 1 replies (of 1 total)

The topic ‘Select2 Error’ is closed to new replies.

 * ![](https://ps.w.org/ultimate-member/assets/icon-256x256.png?rev=3160947)
 * [Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin](https://wordpress.org/plugins/ultimate-member/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/ultimate-member/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/ultimate-member/)
 * [Active Topics](https://wordpress.org/support/plugin/ultimate-member/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/ultimate-member/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/ultimate-member/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [runofthemill](https://wordpress.org/support/users/runofthemill/)
 * Last activity: [9 years, 9 months ago](https://wordpress.org/support/topic/select2-error/#post-8156025)
 * Status: not resolved