jAlert call broken in Exit Notifier 1.5.3?

Hi, Collin! Are you by any chance running a caching plugin? The file name changes have been an issue at a few sites. If you are, please uninstall (make a note of your custom settings, they will go away on uninstall…) and then reinstall from the WordPress plugin site. Once complete, please completely flush your cache and try again.

If that doesn’t change the situation, I’ll be glad to keep troubleshooting with you.

Another helpful piece of information would be if there are any errors popping up in the developer console when no popup appears.

Thanks!

Curtis,

Thanks for the quick reply! I downloaded the latest version of your plugin directly from the plugin page and installed it manually so I don’t think that’s the issue. There’s also no error messages in the console. I even uncommented the console.log calls in the frontend.js file and the console stayed empty.

I don’t think caching is the issue. I’m running it on a local XAMPP server and I don’t think there’s caching built into it. I also don’t think it’s a browser caching issue. I’ve opened my test site with browsers that haven’t gone to that site before and I’m seeing the same issue.

The only thing that made it work again was swapping those two files. Is there something else in the background that might be affecting it?

Thanks,

Collin Condray
Director of Technology
BlueZooCreative.com

No error messages in the console? Do the links work? If they do, I wonder if it’s a situation with the jQuery selector? Are you using a custom one, or the default?

If you view source and look at the header, you should find reference to the frontend.js file form the exit-notifier plugin folder. Directly above it, you’ll find <script> tags, and in there you’ll find the var ExitBoxSettings line with all the Exit Notifier settings. Can you copy paste those here? If you’re not comfortable with that, you can email me at wpplugins (at) cvstech (dot) com.

Also,the reason I’m concerned about caching, is that I had a user with a caching plugin (WP Fastest Cache in this case) that adds all of the js into a single include file, and it had the old jAlert cached and I’m using version 3 of jAlert in 1.4 and version 4 in 1.5 and later. In this user’s case the cache completely broke because it had the old functions instead of the new due to the cache. Not the fault of the plugin, just a bad interaction.

Anyway, that sounded similar to your original post, but I think that’s not the direction based on your update.

Curtis,

I did have a Custom display set. The links weren’t working then. When I switched back to the default display, the popup started working again. The classes on the list didn’t change. Are they supposed to when you use a custom display?

Thanks,

Collin Condray
Director of Technology
BlueZooCreative.com

I only thought about the selector because if there were no errors and not popup, that means that something wasn’t even flagging the links correctly. Can you send me your custom selector and I’ll see if something I changed affected how it’s working?

I didn’t add any selectors, just some CSS to change a few colors. The custom display I was referring to was under the Display tab. I changed the theme to Custom and it stopped working. All of the other preset themes I tried worked for me.

Anything else I can check?

I wouldn’t expect CSS to have that effect… Not sure what to tell you on that one without a look at it directly. If you want to send me your custom CSS I’ll be glad to take a look…

In looking deeper, I think the custom setting might not be accounted for in jAlert version 4. That may have been a modification I made to v3 specifically for the custom setting. I’ll see what I need to do to get that working again.

OK, I’ll hang tight until there’s a new version available. Thanks again for helping me with this!

Hey, Collin, I won’t have that fixed until I’m through testing my next upgrade, and I’ve got a fairly widespread change coming, so it’s likely to be a bit. In the meantime, I think I’ve got a fix for you. I forgot to assert the default entry, so until you go make a change to the Custom CSS and hit save, it won’t carry the changes through. That may be what you were seeing. Can you go make any small adjustment to the CSS in that field and hit save and try again?

You can also see if the ja_custom style from that textbox is making it into the header, it should be one of the last parts of the <head> section right before the body. I was seeing the following:

<style>.ja_custom {}</style>

But it wasn’t causing a problem for me since I wasn’t using custom at the time.

Let me know if saving that page fills the .ja_custom style for you.

I tried making changes to the Custom CSS and Advanced Custom CSS fields and the .ja_custom style did not appear in the header. I even completely removed all of the CSS and the exit popup didn’t appear. Please let me know if you think of anything else I can try until the new version is out. Thanks again for your help on this.

Thanks for the feedback, Collin. Basically, until I get the update out, you’ll need to use one of the built-in styles. I’ll get the next version out as soon as I can.

OK, I’ll be on the lookout for it. Thanks!

Custom theme should be back online now in 1.5.4! Please test and confirm when you can. Thanks for helping me figure that one out. I’ve credited you in the changelog.