Curtis V. Schleich

Hi, @tinpeas! I’m working on ironing out a few security concerns with the WordPress Plugin team. As soon as I can get those issues ironed out, it will be back. I would hop within the next week or so. In the mean time, if you’d like to try the new version as a download, please feel free to email me at the address in the footer of the Exit Notifier settings pages.

Hello, @gopar3! Thanks for the kind words! I have plans, but time has been the problem. I’ll shuffle this up in my stack, an update is long overdue. I can’t make any promises on a time frame, but I do really want to make some changes and updates.

Hello @ssperling! I will do my best to make the changes needed to get this plugin compliant in the next few weeks. It’s long overdue! Thanks for the bump!

Thanks! I can’t make any promises, but I’m hoping to get a minor update out soon to make sure it’s compatible with the current WP releases, and hopefully a complete rewrite later in the year. It’s certainly time. Thanks for the bump!

Hello, @mcarusi! You’re not wrong about it basically being abandoned. It wasn’t my intention, but I hadn’t realized how long it’s been since my last update. I was hoping to make a version 2 and got too ambitious, and swamped with other paid projects.

I’d love more information if you have it about whatever intrusion happened. If my plugin is to blame, I would certainly want to fix it. Thanks for any information you can provide!

This plugin is sorely in need of an update. I will check into this as soon as I can, but paid work is keeping me very busy these days. My apologies for the stale code, and I’ll see what I can do. Unfortunately, I can’t promise anything specific as far as a timeline is concerned.

Thank you, @ssperling, for bringing it to my attention! I will reply here once I have pushed a desperately needed update.

Can you email me (check the bottom of the settings pages in Exit Notifier settings) so I can get some more specific information, like which links in particular work on desktop but not mobile?

Thanks, @ablackburn85!

I’ll do that in the next week or so. Thanks for your willingness to help!

Well, this is the first I’ve heard of my plugin having any kind of impact on posts. None of my code touches posts or pages at all, it’s almost exclusively frontend javascript. Is the site still available for me to look at? I would be interested to find out what the actual cause could be. I obviously don’t want to be negatively affecting people’s sites!

And I was going to be offended at the accusation of abandonment, but I can’t fairly object when I realize when the last update was. Guilty as charged, and I hope to remedy that soon.

Thanks for the kick in the pants, @jakours2! It was a fair shot, and I’ll see what I can do to get a fresh version out soon around my paid work.

Yes, I’ve been buried under paid work. ??

I had bigger plans for a version 2 that have not materialized, but I need to lower my gaze and get a version 1.10 going. I can’t make any promises, but I hope to get back to it sometime soon.

Hello @lescompa! Unfortunately, I’m not familiar with translations, so I’ll have to look into that. Any pointers you can give would be welcome!

So sorry @mumbowebdesign! I have been hoping to get back to this plugin for quite some time, but my paid work has not allowed it. I’m sorry to hear it seems to be conflicting with DIVI. Is this a paid or free version of DIVI?

If I’m way too late, I totally understand. Again, sorry to leave you hanging.

So sorry to not respond earlier, @absherwood70! I think we can achieve what you’re looking for, but I need to understand better. Can you give me a more specific example? Do you want a message any time /ct2 is accessed? Are you considering the /ct2 folder a different site for the purpose of this example?

Also, the link you included doesn’t seem to work. Let me know, and if you’d prefer to get more specific in email rather than a public forum, my email address is at the bottom of every settings page.

Thanks!

Thanks so much, @mreall! I will definitely include this or something like it in my next update.

Very nice workaround to an issue that I know has been a problem before.

Try using jAlert instead of SweetAlert and see if that works better for you. Let me know what you find out, please!