• Resolved dannidar

    (@dannidar)


    I had commented on another’s post, but thought I should do the right thing and open my own thread instead of jumping on an old one!
    First off, I love the plug-in…thank you for all of your hard work and support!
    The only issue I am having is an issue that seems to be occurring frequently with other users as well. I am using the latest version of the plugin, 1.6 I believe, and WP 4.1. I have tried deactivating all of the other plugins and also with twenty fifteen and twenty fourteen themes. Still the same issue:
    I only want the pop-up to open automatically on a specific page. I am able to select that page from the targeting conditions, but upon saving the changes, the selected reverts back to “all pages” … same with “posts” “categories” etc. I even tried excluding all pages but one and it reverted back as well.
    Ideally, I would like to be able to select the targeting conditions from the editor, but if there’s a quick fix to allow the pop up to auto open on a single page, please let me know.
    Thanks so much!

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

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

    (@danieliser)

    Hey dannidar, Please see my response on your other ticket.

    The issue has been resolved officially, the bug was found and patched. but the release has been held up by a few other issues that we are currently working out.

    Thread Starter dannidar

    (@dannidar)

    Thank you so much!
    So, I was able to get it to work in Firefox properly, and that’s perfect for now, until the official update is ready.
    I tried making the additional changes required for Chrome as well, but I’m assuming that I just made some sort of error there because that ended up a mess! ??
    I really appreciate your time and attention to this, and love the plugin!
    Have a wonderful day!

    Plugin Author Daniel Iser

    (@danieliser)

    Yea strangely enough Chrome does some funky things when it comes to using .prop and .removeProp.

    Since the major features of v1.2 are stalled a bit Im about to push out a quick patch version 1.1.7 which will contain this and several other bug fixes. Look for it in about 20 minutes.

    Plugin Author Daniel Iser

    (@danieliser)

    Just pushed out a small update since 1.2 is stalled, v1.1.7 should fix this issue.

    Marking the issue resolved as the bug was found and quite obvious. There should no longer be any issues with this.

    If you still have an issue feel free to post it here and I will revisit the issue.

    I was having the same issue and just performed the update but it still reverts to “Load on All Pages” for me.

    Plugin Author Daniel Iser

    (@danieliser)

    Hey Scrapy, would it be possible to get temporary admin access to try and determine what is going wrong? Have you tried multiple browsers? As some of the bugs were browser specific.

    Hi Daniel,

    I just tried again using Safari and it worked. The issue occurs when using Chrome.

    Plugin Author Daniel Iser

    (@danieliser)

    Ok I will further need to do some checking why it wouldn’t work in Chrome.

    I thought I had Chrome sorted out as thats what we use, but there may be some weird issues maybe in an older version or perhaps some changes didn’t get saved for some reason.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Targeting Conditions not working’ is closed to new replies.