• Resolved seebrosky

    (@seebrosky)


    The latest version(s) of 1.4 are totally busted. Once installed, I can no longer make saves to existing popups, cannot access the WordPress Screen Options, cannot edit trigger or cookie settings AND editing in Visual Composer is no longer available. What the hell, man??

    I have installed every quick release version up to 1.4.5 and none of the above issues have been resolved. I am quite disappointed with what is called an upgrade when basic functions no longer work. I have since reverted my sites back to version 1.3.9 until your crew releases a fully tested, fully functional version that is, at the bare minimum, as good as the older version.

    https://www.ads-software.com/plugins/popup-maker/

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Author Daniel Iser

    (@danieliser)

    @seebrosky – First let me say we had this in public beta for over 2 months. None of the issues that surfaced today were ever reported, so we did do our best to ensure this didn’t occur. Just means we need more beta testers in the future, so I hope you will consider signing up for our mailing list to help when those come out. Also this version is 10x the previous versions, but when introducing new features into a WP environment we can’t account for every plugin/theme available and all the crazy things that they could be doing.

    Ok so it sounds like a JS bug / error for sure. I have tested along side Visual Composer and didn’t see any issues directly, can you get me a list of plugins / theme your using currently. I know you have already went back, but you didn’t by chance check the browser console for the JS errors did you? If not the only way to possibly resolve it would be to get those errors or wait for someone else to maybe report them.

    If possible to get temporary admin access you can submit a support ticket at https://wppopupmaker.com/support with the info. I can then see exactly what is going on and get a solution into the patch I am preparing now.

    Hope that helps, and rest assured they will get resolved quickly, but as I said we can only test it so much before we just have to get it out there. Just an FYI also v1.4 released 24 hours ago, we have been patching the entire time based on feedback so within another day or so all should be resolved. We haven’t seen any issues that weren’t quickly resolveable.

    Plugin Author Daniel Iser

    (@danieliser)

    Oh and just to elaborate this wasn’t an “update” this was a massive “upgrade”. No functionality was removed, only added to, no breaking changes in usability/function were introduced only added to. All deprecated filters were properly marked and we even reapplied the old filters to new ones. This was a 5 month painstaking process, but as with every major release (1.0, 1.1, 1.2.,1.3 etc) the first 2 days are patch patch patch, no way to predict all the unpredictables that occur in WP sites, that is just something we have to deal with as we come to it. But before beta we tested on every version of WP back to what we support (3.4), tested all versions of PHP that are still supported by WP officially, tested dozens of migrations from old version to new etc. Then we went to public beta and had over 200 installs, all reported issues patched. Then we released. Not much more I can do about these issues but try to patch them quickly.

    Look at the change logs for v1.4 and you will see that this is a better product in general, but all of the new code was written to reduce error proneness and increase flexibility.

    Know that I will be working these things out until they are gone, its the only plans I have for now…

    Thread Starter seebrosky

    (@seebrosky)

    Submitted a support ticket with screenshots of site details and console errors.

    Plugin Author Daniel Iser

    (@danieliser)

    @seebrosky – Just checked, I didn’t see one in my support que just now mentioning visual composer, but found it in Gravity Forms, one more thing on my list to check this week, In any case check the response and let me know if that makes since. I definitely want to get this worked out for you in any case.

    Thread Starter seebrosky

    (@seebrosky)

    TEMPORARY SOLUTION: For anyone having a similar problem, Daniel and I narrowed the issue down to a JS conflict between the plugin Ultimate Addons for Visual Composer and Popup Maker.

    To resolve the JS conflict I went into the settings for Ultimate Addons and toggled to ‘OFF’ the option for Woocomposer. Settings path: Ultimate > Modules > Woocomposer.

    Plugin Author Daniel Iser

    (@danieliser)

    @seebrosky – Haven’t tested with this particular plugin but did make some changes that should handle the issue. Please test v1.4.7 and let me know, if the issue still exists I will dig into that plugin specifically, but the error was the same as several other reports which are now resolved so fingers crossed.

    Plugin Author Daniel Iser

    (@danieliser)

    @@seebrosky – Check with v1.4.7, there should no longer be any conflicts with any other plugins using Select2. I now run a sandboxed version independent of what others load.

    Hope that helps, Please take a moment to rate and review the plugin and or support once you have updated to the latest version.

    Visual Composer is broken for me too, and on this site I don’t use Ultimate Addons

    Plugin Author Daniel Iser

    (@danieliser)

    @troglos – Can you elaborate?

    when Popup Maker is activated, Visual Composer is not loaded anymore in the backend, and I see all the tags in the editor.

    Plugin Author Daniel Iser

    (@danieliser)

    @troglos – Hmm, we didn’t change anything in our VC integrations, are there any JavaScript errors on that page that are preventing it from loading?

    F12 -> Console Tab -> Refresh Page. If you see any click the black arrow to show all the details and paste them here.

    Thread Starter seebrosky

    (@seebrosky)

    @danieliser – Newest version of PM installed and I’ve encountered no JS errors or save issues. Thanks for your efforts!!

    Plugin Author Daniel Iser

    (@danieliser)

    @seebrosky – Awesome! Happy I could help you out. Btw, If you have a moment, I would very much appreciate if you could quickly rate the plugin, just to help us spread the word.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘No longer works with Visual Composer…among other things.’ is closed to new replies.