Title: Plugin Conflict
Last modified: August 22, 2016

---

# Plugin Conflict

 *  [redredphoto](https://wordpress.org/support/users/redredphoto/)
 * (@redredphoto)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/plugin-conflict-69/)
 * Hello… EventRocket is serving a pretty important function for my site and customer
   experience. Unfortunately, it seems to be conflicting with another critical plugin:
   wp-invoice. With EventRocket active, i’m not able to view my list of invoices
   in the other plugin… event rocket seems to be blocking the invoice database query
   that serves up the list I need to see.
 * What can we do about this?
 * [https://wordpress.org/plugins/event-rocket/](https://wordpress.org/plugins/event-rocket/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [Barry](https://wordpress.org/support/users/barryhughes-1/)
 * (@barryhughes-1)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/plugin-conflict-69/#post-5706706)
 * Thanks redredphoto, I see the problem and will make a fix available shortly to
   better accommodate this sort of scenario 🙂
 * [https://github.com/barryhughes/event-rocket/issues/19](https://github.com/barryhughes/event-rocket/issues/19)

Viewing 1 replies (of 1 total)

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

 * ![](https://s.w.org/plugins/geopattern-icon/event-rocket_dacd8c.svg)
 * [Event Rocket](https://wordpress.org/plugins/event-rocket/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/event-rocket/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/event-rocket/)
 * [Active Topics](https://wordpress.org/support/plugin/event-rocket/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/event-rocket/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/event-rocket/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Barry](https://wordpress.org/support/users/barryhughes-1/)
 * Last activity: [11 years, 4 months ago](https://wordpress.org/support/topic/plugin-conflict-69/#post-5706706)
 * Status: not resolved