Title: Avada Theme Conflicts
Last modified: December 25, 2016

---

# Avada Theme Conflicts

 *  Resolved [wpab](https://wordpress.org/support/users/wpab/)
 * (@wpab)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/avada-theme-conflicts/)
 * I’m wondering if you are aware of any conflicts with the Themefusion Avada theme(
   Version: 5.0.6)? I’m not sure if this should be directed to you or them, but 
   perhaps you could provide some insight? These problems only started with Avada
   5.x (pre 5.x all was fine). These issues only happen with your plugin. All else(
   theme functions, other plugins, etc.) are fine.
 * 1. **Can’t assign agents for a ticket from the dropdown.** Using the search in
   dropdown always results in ‘not found’. Ticket is always assigned to default 
   agent (if opened by user) or to the agent who opened the ticket (if submitted
   by an agent)
 * This js error appears in console, and I assume it is related:
 * _Uncaught Error: Option ‘ajax’ is not allowed for Select2 when attached to a 
   <select> element._
 * 2. **Editor will not load when their Fusion Builder plugin (required by theme)
   is enabled.**
 * The editor on the ‘add ticket’ page does not load at all. On some pages it loads
   but is not fully functional. When editing a ticket, the content sometimes does
   not load in the editor. There are no problems at all with the editor on regular
   pages, posts, etc. It only happens within the Awesome Support plugin.

Viewing 9 replies - 1 through 9 (of 9 total)

 *  Plugin Author [awesomesupport](https://wordpress.org/support/users/awesomesupport/)
 * (@awesomesupport)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/avada-theme-conflicts/#post-8595445)
 * Hi:
 * Does this happen with all other plugins disabled? Just wondering if the conflict
   is with AS and Avada or with AS, Avada and something else.
 * Thanks.
 *  Thread Starter [wpab](https://wordpress.org/support/users/wpab/)
 * (@wpab)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/avada-theme-conflicts/#post-8595554)
 * Yes. Also, the problem is not there with Avada version before 5.x
 * As far as I can tell it is a conflict with Avada loading select2 version: 3.5.2(
   from ReduxFramework) and your newer select2 version: 4.0.2.
 * I tried to modify your ACF Pro fix but I probably did it wrong and it didn’t 
   work.
 *  Thread Starter [wpab](https://wordpress.org/support/users/wpab/)
 * (@wpab)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/avada-theme-conflicts/#post-8596139)
 * FYI, Just to double double check, I just tried a new clean localhost test install
   with no plugins but Awesome Support. It works fine with WP default themes but
   as soon as I enable Avada, the issue is there.
 *  Plugin Author [awesomesupport](https://wordpress.org/support/users/awesomesupport/)
 * (@awesomesupport)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/avada-theme-conflicts/#post-8598868)
 * Hi:
 * I took a quick look at this theme and tried to remove the select2 script the 
   way we have done to maintain compatibility with other plugins. Unfortunately 
   turning off the AVADA select2 script on our pages causes Avada other issues because
   they load a bunch of tabs with settings on the page and those tabs seem to require
   Avada’s version of SELECT2. While I’m not familiar with the theme, I couldn’t
   find a configuration option in the theme settings to prevent Avada from loading
   its configuration tabs on our pages at all. They might have one but I couldn’t
   find it right away.
 * From what I can tell this is not a simple fix and we might never be able to fix
   it unless Avada helps. There seems to be no way to easily prevent them from loading
   their tabs and other code on our pages in wp-admin – not without writing and 
   testing a bunch of other code. Basically we need a more extensive compatibility
   fix than we have done in the past for other plugins. I have added this to our
   todo list to take a look to see what’s possible but right now its not a quick
   fix. The earliest you can expect a compatibility fix would be the end of the 
   first quarter of 2017. I really wish I had better news but I need to turn this
   over to our core developers at this point.
 *  Thread Starter [wpab](https://wordpress.org/support/users/wpab/)
 * (@wpab)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/avada-theme-conflicts/#post-8598907)
 * Okay. Thanks for trying. I’m probably just going to downgrade Avada to 4.x until
   it gets sorted out.
 *  Thread Starter [wpab](https://wordpress.org/support/users/wpab/)
 * (@wpab)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/avada-theme-conflicts/#post-8601962)
 * I have one more question. We need to be able to add inline images via the visual
   editor and I’m seeing some inconsistency.
    - ‘Add New’ loads the standard WordPress post editor and the ‘add media’ button
      works.
    - Ticket replies loads TinyMCE and there is no way to add inline images (in 
      the visual editor).
    - ‘Edit ticket’ loads the standard WordPress post editor but the ‘add media’
      button is disabled.
 * I’m not seeing any errors so I assume this is the way you have it set up.
 * Is there a way to fully enable inline images?
 *  Plugin Author [awesomesupport](https://wordpress.org/support/users/awesomesupport/)
 * (@awesomesupport)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/avada-theme-conflicts/#post-8604765)
 * Hi – Can you start a new thread for your new question? I’d like to keep this 
   one on the Avada topic since we’re still working on the issue. We started a dialog
   with them and received a reply that they would take a look at the issue. Of course,
   no time line was given but at least we got a reply.
 * I’ll keep you updated when we get a new response from them.
 * Thanks.
 *  Thread Starter [wpab](https://wordpress.org/support/users/wpab/)
 * (@wpab)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/avada-theme-conflicts/#post-8604904)
 * Sure.
 * In case anyone else is having this problem (before a fix is done) Awesome support
   does work fine in Avada 4.x so downgrading will work as a temporary fix.
 *  [AkaruMaster](https://wordpress.org/support/users/akarumaster/)
 * (@akarumaster)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/avada-theme-conflicts/#post-9102303)
 * You can update file
    \themes\Avada\includes\avadaredux\avadaredux-framework\AvadaReduxCore\
   assets\js\vendor\select2.min.js
 * from version 3.5.x to the last Select2 4.0.3
 * [https://github.com/select2/select2/](https://github.com/select2/select2/)
    -  This reply was modified 9 years, 1 month ago by [AkaruMaster](https://wordpress.org/support/users/akarumaster/).

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘Avada Theme Conflicts’ is closed to new replies.

 * ![](https://ps.w.org/awesome-support/assets/icon-256x256.png?rev=1849681)
 * [Awesome Support - WordPress HelpDesk & Support Plugin](https://wordpress.org/plugins/awesome-support/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/awesome-support/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/awesome-support/)
 * [Active Topics](https://wordpress.org/support/plugin/awesome-support/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/awesome-support/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/awesome-support/reviews/)

 * 9 replies
 * 3 participants
 * Last reply from: [AkaruMaster](https://wordpress.org/support/users/akarumaster/)
 * Last activity: [9 years, 1 month ago](https://wordpress.org/support/topic/avada-theme-conflicts/#post-9102303)
 * Status: resolved