Title: Incompatible with Ultimate CMS plugin
Last modified: August 21, 2016

---

# Incompatible with Ultimate CMS plugin

 *  [SeanBanksBliss](https://wordpress.org/support/users/seanbanksbliss/)
 * (@seanbanksbliss)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/incompatible-with-ultimate-cms-plugin/)
 * When both of these plugins are active the landing page plugin can not show you
   the editor, it shows up as a blank screen. Any chance you for working in a future
   compatibility? Might be nice to use both plugins at once?
 * [https://wordpress.org/plugins/landing-pages/](https://wordpress.org/plugins/landing-pages/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [David Wells](https://wordpress.org/support/users/davidwells/)
 * (@davidwells)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/incompatible-with-ultimate-cms-plugin/#post-4634137)
 * What is the issue?
 * Would need more background info to diagnose the cause.
 * Sounds like you have a javascript error caused by another plugin or by your theme.
 * To check for javascript errors go to the screen you are having the issue with
   and follow this video:

Viewing 1 replies (of 1 total)

The topic ‘Incompatible with Ultimate CMS plugin’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/landing-pages_88766e.svg)
 * [WordPress Landing Pages](https://wordpress.org/plugins/landing-pages/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/landing-pages/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/landing-pages/)
 * [Active Topics](https://wordpress.org/support/plugin/landing-pages/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/landing-pages/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/landing-pages/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [David Wells](https://wordpress.org/support/users/davidwells/)
 * Last activity: [12 years, 3 months ago](https://wordpress.org/support/topic/incompatible-with-ultimate-cms-plugin/#post-4634137)
 * Status: not resolved