• Resolved dvuksanovich

    (@dvuksanovich)


    Hi,

    First off, love the plugin. Working great in my test environment so far except for one small issue:

    The “Not On Specific URL” rule isn’t working the way I would expect it to. I’m using permalinks for my blog posts that are just [domain]/[post]. I don’t want the popup to show on my homepage, but I do want it to show on all my blog posts. The problem seems to be that the rule is not looking at the absolute URL, but whether the string is contained within the URL being visited.

    For example, here are two URLs on my site:
    https://mysite.com (home page)
    https://mysite.com/blog-post-number-one/ (blog post)

    If I specify “Not On Specific URL” and include the home page URL, the popup doesn’t show on any of my blog posts. If I remove the home page URL from the “Not On Specific URL” list, then the popup shows on my blog posts.

    Is this by design? If so I will not be able to use the plugin because of my permalink structure.

    Thanks in advance for your help.

    https://www.ads-software.com/extend/plugins/wordpress-popup/

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter dvuksanovich

    (@dvuksanovich)

    I should mention that if I can get this thing up an running properly I’m going to write a blog post about calls to action and will be linking to the WPMU site from the article.

    Hi @dvuksanovich,

    Thanks for the information here. There does seem to be some kind of quirk with the URL based rules and we need to pin it down to something specific so that we can fix it… this might be the clue we needed.

    Would you mind running an experiment for us? Could you use a different URL in the “Not on Specific URL” rule, check the PopUp doesn’t show there, and make sure it does show on other pages.

    Also, if your site structure allows it, could you test if sub-pages or query strings are affected?

    i.e.
    Set the rule on /category/
    Then check /category/post
    and /category/?test=1

    I’ll run some tests my end too and we’ll see if we can pin this down for a patch.

    Thread Starter dvuksanovich

    (@dvuksanovich)

    I’ve already tested the first one. There are other pages besides my home page that I’ve set for “Not On Specific URL” and they work fine. It’s only when I add my home page to that list that I start having problems. That’s why I started thinking that whatever regular expression matching you’re using wasn’t looking at whole URLs, but doing some sort of “contains” comparison.

    As for sub-pages and query strings, I don’t use either on my site. Sorry.

    Thanks for the extra info. I’ve linked the developer to this thread for reference. He has agreed to see if the regular expression matching can be tweaked to better accommodate this situation. I’ll let you know what he comes up with!

    Hi @dvuksanovich,

    Just wanted to give you an update on this. We’ve got a new build being tested at the moment, and we’ll have an update ready for release here very soon.

    Thanks for your patience, and for pointing out a bug that definitely needed fixing.

    Thread Starter dvuksanovich

    (@dvuksanovich)

    Thanks for the update. I look forward to testing the new version once it’s released.

    Version 4.4.5.1 is now live and specifically addresses this issue! Go get it!

    Let us know if for any reason this problem persists… otherwise please kindly mark the thread as resolved.

    ??

    Thread Starter dvuksanovich

    (@dvuksanovich)

    It works. Nicely done.

    Thanks!

    Not sure if I should start a different thread but I’m using the latest version (4.4.5.1) and the problem is still there.

    The popup still appears when I specify the following ‘Not on specific’ URL:
    https://domain.com/login/?redirect_to=%2F

    As this thread is marked as resolved… please start a new thread providing any details you can regarding your settings etc and we’ll take a look for you.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘"Not On Specific URL" Problem’ is closed to new replies.