Support » Plugin: Popup Maker - Popup for opt-ins, lead gen, & more » conflict with editor and other errors

  • Resolved rafa01

    (@rafa01)


    Fatal plugin updating.
    I´ve had to desactivate this plugin becouse has broken several things in my Web.
    Don´t show the Wysiwyg. Bad behavior of the popup and so on.
    Please come back to the previus version

    • This topic was modified 6 years ago by rafa01.
    • This topic was modified 6 years ago by rafa01.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Daniel Iser

    (@danieliser)

    @rafa01 – Sorry to hear,that said not enough info honestly.

    The broken editor is 99.99% gonna be due to your browser caching not loading the latest version of our admin JS. Not sure why that is happening but CTRL+F5 has fixed it for most.

    Also if you processed upgrade routine in the admin dash you won’t be able to go back without recreating the popups or restoring a backup. The data structure has changed. So the best bet is to list the issues with as much detail so we can get them resolved.

    christoschiotis

    (@christoschiotis)

    Same problem with the editor here.
    I tried de-activating every other plugin and popmaker produces this error in Console

    View post on imgur.com

    Of course tried all the possible clear-caching ways
    I reinstalled core wordpress files

    thisisbolo

    (@thisisbolo)

    Anyone else experiencing this plugin producing major 503’s since the last update? I turned on debug to log and it was riddled with errors.

    Plugin Author Daniel Iser

    (@danieliser)

    @thisisbolo – Nope, so far since the last patch nobody has been reporting additional errors, but if you have logs we would love to see them. Also that would definitely warrant its own new topic ;).

    @christoschiotis – Sorry to say but the only option currently appears to be that it is a caching issue. To clarify the file that is shown to generate an error in your image of a missing variable of pum_shortcode_ui, doesn’t currently in the new version actually contain any lines referencing the pum_shortcode_ui variable. We renamed it to pum_shortcode_ui_vars, which means your browser is still trying to use the old copy which no longer exists in our code. There simply isn’t another explanation unless your plugin files have become corrupted some how in which case reinstalling the latest would resolve it.

    Hope that helps.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘conflict with editor and other errors’ is closed to new replies.