David Aguilera

Thanks for the heads up! We already applied the fix and we’ll include it in our next release.

Awesome, thanks for confirming!

Good morning! Thanks for reporting the issue.

I’m quite surprised this problem showed up, because it doesn’t on any of our development environments nor our own website…

Anyway, we’ve added a safe guard in the plugin that should address and fix the bug. It’s available in version 7.2.1. Would you please be so kind to upgrade and let us know how it works?

I tried to recreate the issue locally with no luck. Regardless of the form’s settings (AJAX vs no AJAX) and our plugin’s setup (redirection vs cookie alternative loading, hide/show query args, preload/no preload query args, etc), I was able to see the confirmation message of my WPForms at all times.

If you could please share your specific setup, I’ll try to recreate it locally once again and see if I can reproduce the issue. Otherwise, I’ll be marking this topic as resolved.

Hi! Thanks for getting in touch with us.

There’s only one thing I can think of: if the form is not submitted via AJAX, is possible that the following sequence occurs:

1. The visitor lands on https://example.com/tested-page/. Let’s say she’s supposed to see variant B, so…
2. Our plugin redirects her to https://example.com/tested-page/?nab=1
3. She fills in the form included in the tested page
4. She submits the form. This submission is not performed using AJAX – it’s a regular POST request, and so, upon submission, the current page is reloaded, so the visitor lands on https://example.com/tested-page/ (which includes the confirmation message)
5. Since this page is under test, our plugin notices this and redirects the visitor to the appropriate variant again, https://example.com/tested-page/?nab=1, which means the confirmation message has been lost.

Would you please be so kind to recreate the test and check if that’s the issue? If that’s not the case, or if you’d rather have me look into it, please send us an email to support at nelio software dot com and we’ll investigate what’s happening. In the meantime, we’ll try to reproduce this issue as well in our dev environments.

Cool! I’m glad to hear. However, I must warn you: you might end up encountering similar issues in the future when, for example, you’re trying to edit/save a test. All these operations use the REST API I mentioned earlier, so you want to make sure it’s not blocked by other plugins. As I said, if you want us to take a look at it, just let us know. In the meantime, though, I’ll mark this issue as resolved.

Hi! Are you using, perhaps, a firewall or security plugin? If you are, it might be blocking our REST API endpoints.

Try the following: open your browser’s web developer tools and go to the Network tab. Then, click on “Continue” and look at the request that shows up in the Network tab. Does it fail? What does it say?

If you want me to look into it, please send as an email to info at nelio software dot com and I’ll be happy to.

Hi! I don’t know what could be amiss. Heatmaps are rendered in your browser using an iframe, so I’d need to take a closer look at your setup to understand what’s going on.

Please contact us via email (support at nelio software dot com) and we’ll discuss how to proceed.

For anybody else experiencing this issue: keep in mind that the global object nab might not be available because our tracking script may not be included in the current page. This occurs, for example, when previewing variants. So you gotta make sure that, whenever you want to use nab methods, you first make sure that nab exists by wrapping it in an if statement like this:

if ( window.nab ) {
  nab.blahblah
}

Did you enable the option “Test against already existing pages”? Because, if you did, that’s the intended behavior — there’s two pages that are already published on your website and you simply tell our plugin to test one against the other.

If you wanted both variants to use the same URL, you need to uncheck the aforementioned option and create your B variant within the scope of a test. It’ll start as an exact copy of your tested page, but you can easily tweak it and change its appearance and content.

Indeed, there’s a notice/warning that shows up. It’s not a critical problem and, if I recall correctly, it’s automatically fixed right after it’s been first shown on screen. But we’ll include the fix in our next release anyway. Thanks for reporting!

My pleasure. And thanks for the review ??

Merci beaucoup!

In Nelio Content Settings ? Social Media ? Advanced, there’s an option to add those meta tags. Disable the checkbox and our plugin shouldn’t add them.

Thanks, Jordi. We’ll look into it and get back to you ASAP.