Shay

Hi Deyson,

Just wanted to follow up to let you know that we’ve just released a brand new version of the Leadin form capture tool which now means that we can successfully capture submissions on Easy Digital Download forms. In order for this to work, the ‘Enable Ajax’ option under Settings > Misc in EDD needs to be unchecked but both Leadin and EDD will work if this is disabled.

Also worth mentioning, as per above, that this will only work if there are no sensitive fields on the forms such as credit card fields since Leadin will never collect a form that contains sensitive information.

Thanks again for reaching out. If there is anything I can clarify please let me know.

Thanks for taking the time to write this review and for sharing Leadin with others. It’s awesome to know that you are already seeing value, we really wanted it to be as little effort as possible to set up, and provide immediate results so it’s great to hear that’s the experience you had.

Hi Nathaniel,

Thanks for reaching out! There is indeed a way to disable notification for certain forms. This guide should walk through how to do this, you’ll see a Notifications button on each form in Leadin.

I hope this helps, let me know if there is anything I can clarify.

Hey adrianifero, thanks for reaching out! I’ve added you down on our list to keep posted on this integration. While it’s not on the short term roadmap for the tool, it’s definitely something that’s high on our radar and would likely be next in line for our email integrations. As we have more info I’ll definitely keep you posted here.

(A little backstory here, since this original post we’ve actually rebuilt Leadin on a whole new infrastructure that allows us to offer a much more robust and reliable version of Leadin, and cloud based for security. This rebuild took a lot of time and focus on our end so while it seems like it’s been a while since this initial post, we’ve actually been hard at work ?? )

Hi mapcom,

Thanks for reaching out! At the moment I’m afraid that it’s not possible to translate the Leadin popup forms but this is something that we’re actively working on at the moment and we hope will be possible in the not too distant future. I can keep you posted as we have news on this if that works for you?

Thanks,
Shay

Hi Henk,

Just wanted to give you a heads up that we’ve just released version 4.3.0 of the plugin which should resolve this issue. You should be able to update right from within Plugins in WordPress but if there are any issues or if this doesn’t solve it for you definitely let me know.

Thanks again,
Shay

Hi Henk,

Thanks for reaching out and letting us know. We’re working on a fix for this right now and should have an update for the plugin out shortly. I’ll let you know as soon as it’s ready to download. From my testing just now, it looks like this shouldn’t be an issue in most themes, with browsers adding in a space automatically, but it’s likely that some more complex themes like Sage have a problem with it.

Thanks again for letting us know and for the detailed breakdown of your troubleshooting.

Thanks Cristian, just responded to you there so I’ll close this thread and we can continue to work on this via email and hopefully get to the bottom of it ??

Cheers,
Shay

Hi there, based on the error message, this usually means that the database tables have been backed up and restored but that restoration did not include the Leadin database tables. There are 5 of those which all start with li_.

You mentioned that the tables are there and that the data is good, can you confirm if all 5 still exist? There should be li_leads, li_pageviews, li_submissions, li_tags and li_tag_relationships.

If it’s a case that they all do exist, we’ll definitely need to take a deeper look and see if anything has been corrupted or if there is an issue with the database structure. In that case, could you reach out to me at [email protected] with an export of those tables so we can debug further and hopefully get you back up and running?

Thanks,
Shay

Hi Victor,

Been testing this a bit and it looks like the login page that WordPress Social Login use is an altered version of the normal login page which does not include the <?php wp_footer(); ?> function which is how Leadin includes the tracking code and form capture script.

I had a look around the plugin and I couldn’t find a straight forward way to change that and include this code, but perhaps the engineers who built it may know a way?

If there is anything I can do to help definitely let me know.

Thanks,
Shay

Hi Victor,

The Leadin form capture script should be included on the wp-login page by default, so it’s more likely that the Social Login plugin form does not follow the necessary form guidelines outlined in this guide. If you can link me to the plugin, I should be able to confirm for sure.

Thanks,
Shay

(worth noting, even though the Leadin form capture script is included on the wp-login page it will never capture or store anything in a password field)

Hi Victor,

Leadin should be able to collect submissions on the default WordPress login form right out of the box, are you using the default one or a different plugin to achieve login & register?

Thanks,
Shay

Hi Victor,

I wanted to let you know that we’ve been able to get to the bottom of the issue you were seeing earlier, and have since resolved the root cause. You should now be able to successfully create a Leadin account without any problems.

I wanted to apologies for the trouble, we’ve put in some additional testing and checks on our side now to prevent this from happening again in the future.

If there is anything I can do to help or if you have any follow up questions, please let me know.

Best,
Shay

Hi there,

Thanks for reaching out and letting us know about this issue you are seeing. We’re taking a deeper look into this at the moment to establish why you are seeing this. I will keep you posted as soon as we know more and are able to fully resolve it.

Apologies for any trouble caused. Please let me know if you have any questions in the meantime.

Thanks,
Shay

Hi Rebecca,

The newest version of Leadin (v4) was a complete rebuild of the plugin on a new infrastructure, I’m afraid this User Access setting was a setting that did not make it over to the first iteration of the rebuild of the plugin.

At the moment this level of user access control is not possible but we are working on solutions to this. I can keep you posted as we have more information if that works for you?

Cheers,
Shay