sharongraylac

Any word on this? I just finished customizing my first loop, and then I realized it broke my navigation (load on click). I love this plugin, but I’d rather not sacrifice the UX for a pretty skin. I hope there’s a solution. Thanks!

Sounds great. Thanks again!

Yes, I created a cookie for the Click Open Popup. From the instructions above (see 2nd post from from you), I thought I was suppose to create one. Is this true? Or did I misunderstand something?

So I may have ALMOST figured out a way to make it work, but it doesn’t feel stable to me.

I added back the action for the exit intent popup (which has always worked well), and I then I added the js for the click-triggered cookie (since I can’t seem to figure out how to add another action without breaking my site).

Now when I subscribe via the click triggered popup, the exit intent popup is no longer engaging. Hooray for that! BUT, it’s still preventing the click-triggered popup from popping up.

I want that to ALWAYS show if someone clicks it, regardless of whether or not they’ve ever subscribed. I just don’t want the exit intent to engage if someone has already subscribed.

Does this make sense?

Actually, it’s half working, but not in a good way.

Now when you click on the button that opens the click-triggered popup, it shows a black screen with no popup–which is exactly what I wanted to avoid.

And the cookie isn’t stopping the exit intent popup from triggering. So now I’ve got a darkened screen and when I try to leave the page, it triggers the exit intent UNDER the overlay.

I kinda feel like I’m taking crazy pills here. It seems like there’s something simple I’m missing, but I can’t seem to find that missing piece to make it all work.

Thanks for hanging with me, either way.

Sharon

• This reply was modified 7 years, 10 months ago by sharongraylac.

So should I remove this code I received from Daniel and do it this way instead?

And this will make it easier to make the cookie for one popup trigger the cookie for another?

Thanks!
Sharon

Here’s where I’m getting tripped up (in hopes of making this easier)…

Do I need to create a “Manual” js cookie for the click triggered popup?

If so, what do I need to do differently to make the following action work (as it’s currently breaking my site)?

add_action( ‘gform_after_submission_16’, ‘pum_gform_set_cookie’, 10, 2);
function pum_gform_set_cookie( $entry, $form ) {
$date_of_expiry = time() + 60 * 60 * 24 * 365 * 10 ; // Calculates 10 years.
setcookie( “pum-7332-click-triggered-subscribe”, true, $date_of_expiry );
}

Is it breaking because there is already this action in effect?

add_action( ‘gform_after_submission_16’, ‘pum_gform_set_cookie’, 10, 2 );
function pum_gform_set_cookie( $entry, $form ) {
$date_of_expiry = time() + 60 * 60 * 24 * 365 * 10 ; // Calculates 10 years.
setcookie( “pum-7408-subscribe”, true, $date_of_expiry );
}

Thanks a bunch!
Sharon

• This reply was modified 7 years, 10 months ago by sharongraylac.
• This reply was modified 7 years, 10 months ago by sharongraylac.

Nope. Still not working.

Here’s the action I’m currently using for my Exit Intent popup (which seems to be working well):

//Prevent exit intent popup from showing after form is submitted

add_action( ‘gform_after_submission_16’, ‘pum_gform_set_cookie’, 10, 2 );
function pum_gform_set_cookie( $entry, $form ) {
$date_of_expiry = time() + 60 * 60 * 24 * 365 * 10 ; // Calculates 10 years.
setcookie( “pum-7408-subscribe”, true, $date_of_expiry );
}

I tried making a separate action for the new cookie, but that kept breaking my site. So then I changed the bottom line of the original action to:

setcookie( “pum-7408-subscribe”, “pum-7332-click-triggered-subscribe”, true, $date_of_expiry );

This no longer breaks my site, but it doesn’t seem to do anything.

I even consolidated my Gravity Forms so they were both using the same form, but nadda.

I also tried deleting the click-triggered-subscribe cookie from the Exit Intent popup, and only included it in the action (just for the heck of it), and nothin’.

Any idea what I might be doing wrong?

Thanks again,
Sharon

Oooooooh, this is BRILLIANT. Now If I can just make it work. lol

So if I’m hearing you correctly, I just create a cookie for the click-triggered popup, however, I do NOT attach it to the click-triggered popup. Instead, I attach it to the Exit Intent popup.

To do that, it looks like I would need to add that same cookie to exit intent popup as well, otherwise, it won’t let me attach it.

Am I with you so far?

And if it’s a 10 year cookie, I’m assuming this needs to be another manual js cookie. Yes?

Which means I need to add another function specific to that cookie?

Any idea where I’m going wrong?

Thanks a bunch!
Sharon

Thanks, @waltmesser! If I could give you 5 stars again, I would… ??

Thanks for getting back to me, @waltmesser!

So just to make sure I understand correctly, I would have to create cookie for my click-triggered popup to not display after they subscribe, and then apply that same cookie to the exit intent opt-in?

If so, I almost like that idea. I’m just worried about folks clicking a button and nothing happening. If they forgot they already signed up for my list, it just looks like I’ve got a faulty button.

Is there a way to create a manual js cookie within the exit intent popup itself that prevents it from popping up if the Gravity Form from the OTHER popup is completed?

For instance, is it possible to use the following filter, replacing the gform ID from the Exit Intent popup with the gform ID of the click-triggered popup?

//Prevent popup from showing after form is submitted

add_action( ‘gform_after_submission_[Exit Intent ID]’, ‘pum_gform_set_cookie’, 10, 2 );
function pum_gform_set_cookie( $entry, $form ) {
$date_of_expiry = time() + 60 * 60 * 24 * 365 * 10 ; // Calculates 10 years.
setcookie( “[Exit intent cookie name]”, true, $date_of_expiry );
}

Fingers crossed… ??

Thanks again!
Sharon

Yup! That took care of everything! Cookies are working perfectly now. Thanks again!

I’ve already given my own rave review, but I have to say, I agree with @karlwebtips 100%. There’s a bit of a learning curve with cookies and conditions, but it’s SOOOO worth taking the time to get the hang of it. I’ve never been a fan of popups for the same reason karlwebtips mentioned above, but Popup Maker has made a believer out of me after all…

Holy cow, you’re fast!

Your update did the trick! Hopefully that’ll fix my cookie issue…

Thank you, Daniel!!!

P.S. I figured out a work-around, and that’s to use multi-post merge tags, instead of most recent. So don’t worry about this unless it’s important to you.

Thanks so much for the fantastic plugin!