Support » Plugin: Popup Maker - Popup Forms, Opt-ins & More » Possible conflict w/IgniteUp

  • Resolved cudak888

    (@cudak888)


    Hello!

    I just posted this to the IgniteUp support forum, but thought I’d bring it up here, just in case it’s WP Popup Maker that has the code conflict.

    I’m in the process of migrating a site (that has been upgraded and modified on a local XAMPP server) onto a live server for further testing. The earlier version of the site did not have WP Popup Maker, but it did use the IgniteUp plugin for displaying a maintenance page.

    In between the earlier version of the site and the updated version, WP Popup Maker was added – seemingly with no issues.

    However, upon going live and testing the active IgniteUp “coming soon” page on a separate browser, I was quite surprised to find every single one of the popups were displayed – one by one – below IgniteUp’s coming soon page, like a huge inline footer.

    I don’t have the time at present to shut down and turn on plugins to see if this is a like issue on a site running the default theme and these two plugins alone, but I thought I’d mention it – just in case.

    -KK

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Hello @cudak888:

    Here’s a link to a nifty plugin built by the development team at WordPress.org: Health Check. You can run it on your production site, and in Troubleshooting mode, it will allow you to deactivate and systematically reactivate plugins and switch themes without disturbing the front end for any user other than you. See what results you get.

    Without a site URL to inspect, I can’t determine what else might be going on.

    • This reply was modified 2 years, 9 months ago by Robert Gadon.

    Unfortunately, I didn’t have time to leave the site in that state and had to switch over to the Maintenance plugin for the moment.

    I dare say it’ll probably give the same trouble on the local XAMPP copy, so I’ll give it a try today and examine the code (and test it with Health Check).

    Sharing the URL may not be possible as it’s a client’s website, but I’ll see what I can do. If its repeatable, I may be able to take one of my own sites and force the error temporarily for your benefit.

    -KK

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Possible conflict w/IgniteUp’ is closed to new replies.