Title: Avada Conflict
Last modified: December 20, 2016

---

# Avada Conflict

 *  Resolved [lizzy2surge](https://wordpress.org/support/users/lizzy2surge/)
 * (@lizzy2surge)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/avada-conflict/)
 * Hi, the plugin is conflicting with Avada. I tried your information [here](https://wpjobmanager.com/document/dealing-troublesome-themes/),
   and it is still not working. It makes the links not work, so you can’t apply 
   or view a job. Anytime I add any of the styling for Avada, like the header and
   such, it breaks it. Is there anything you can do to help? I’m interested in purchasing
   an add-on for this, and would like to use your plugin, since I seem to be running
   into issues for other job board plugins as well.

Viewing 1 replies (of 1 total)

 *  Plugin Contributor [jonryan](https://wordpress.org/support/users/jonryan/)
 * (@jonryan)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/avada-conflict/#post-9197055)
 * [@lizzy2surge](https://wordpress.org/support/users/lizzy2surge/) did you get 
   this resolved? If not enter a presales question at wpjobmanager.com/support and
   we can look into this since Avada is pretty popular.

Viewing 1 replies (of 1 total)

The topic ‘Avada Conflict’ is closed to new replies.

 * ![](https://ps.w.org/wp-job-manager/assets/icon-256x256.gif?rev=2975257)
 * [WP Job Manager](https://wordpress.org/plugins/wp-job-manager/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-job-manager/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-job-manager/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-job-manager/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-job-manager/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-job-manager/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [jonryan](https://wordpress.org/support/users/jonryan/)
 * Last activity: [8 years, 11 months ago](https://wordpress.org/support/topic/avada-conflict/#post-9197055)
 * Status: resolved