Support » Plugin: Popup Maker - Popup Forms, Opt-ins & More » JS issues after last update

  • Resolved patrickhealy

    (@patrickhealy)


    I installed the most recent version and it seems to be butting heads with LiteSpeed on the caching front. Got a bunch js errors. Has anything changed in the way the js is formed? It was working beautifully just moments before and goes back to working when LiteSpeed is deactivated.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Not only last update 1.7.18 but 1.7.17 as well.
    I reverted back to 1.7.16 to solve the issue.

    Plugin Author Daniel Iser

    (@danieliser)

    @patrickhealy, @bajsolinowich – 1.7.17 had a typo that may have generated JS errors randomly depending on Popup settings. That said v1.7.18 was pushed without the typo just a few minutes later so it should not still exist once you have updated.

    Otherwise I would need to see the errors to know what is going wrong beyond the typo that no longer exists. I just checked and nothing else changed in the front end JS or asset system since v1.7.16 except that a typo was added in 1.7.17(that typo was the only modification to that file), and removed in 1.7.18. So the front end JS in v1.7.16 is exactly the same as 1.7.18.

    Maybe purge site & browser caches?

    Let me know where I can see the issues if they persist.

    Looks like that last push did it. I updated and cleared the cache and it all seems to be working properly now. FYI, the plugin being used in tandem is MaxButtons. We are launching a popup off of a style we put in the button so when you click on it, it triggers Popup Maker.

    Not sure if you tend to monitor popular plugins that are used with this one but that one is a really good complement to this since they started messing with the sharing aspect of the button. It lends itself now to just using the button as a button and setting your own triggers and abandoning much of the rest of the plugin.

    Confirmed.
    V 1.7.19 works like a charm.
    Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘JS issues after last update’ is closed to new replies.