Andy Cook
Forum Replies Created
-
Do you have a non-404 page to test those same forms on? If you look at the Javascript there’s an error, so it could be that the 404 page template is breaking Leadin.
Sorry about the issues. Which form are you asking about specifically? The popup form or the newsletter sign up form in the sidebar?
Thanks!
@ripplekindness – Thanks for letting me know and sorry about the issue. We seem to be running into an issue with some Gravity Forms that I haven’t been able to figure out yet. I’ll try to compare all the different forms and see if I can find the pattern for why this type of form isn’t working correctly.
That makes sense. Can you send a screenshot of your comment form and the submission to support@leadin.com?
@tommartinnola – So just to clarify… you mean the Online Course Registration form isn’t working correctly, right? If that’s the case, then I’m not really sure why it isn’t working… I tested a local Gravity Form using the latest version, and also ripped down the HTML from your form too to check that, and it all seems to be compatible with Leadin. I’m a bit stumped here to tell you the truth.
The NEVER MISS AN UPDATE form isn’t actually going to work because there’s an onsubmit event bound to the form tag running some validation checks that is going to interfere with Leadin.
@ tommartinnola – hmm – I looked at the source code and I’m not sure why it’s not working. I’ll try to getting and updated copy of Gravity Forms this weekend and see if I can replicate the problem.
Hi Marilyn –
Leadin will catch partial form submits that don’t make it through form validation, so it’s possible that the person here filled out her email address and a comment, but left out her name, which would save the submission to Leadin but stop the commenting from being submitted because it doesn’t pass the validation tests.
Did the comment have all the required fields for the native WordPress form?
To close the loop for others, this ended up being the form widget having an “onsubmit” event bound to the form element.
The Javascript onsubmit event blocks Leadin’s ability to hook into the traditional form submission process. We’ll hopefully have a workaround for this type of form in the future, but right now the fix is to switch to a more traditional form that submits via HTML.
So I realized that this issue happens even when the AWeber Connect power-up isn’t enabled.
If you’re not actually using AWeber, you can safely comment out line 37 in /wp-content/plugins/leadin/power-ups/aweber-connect.php and your Divi Builder should start working again until we launch the fixed version. Usually I would say to never modify the source code of a plugin, but since we’re launching a fixed update to this bug it shouldn’t matter your changes are overwritten.
To comment out that line, all you have to do is open the file on your server in a text editor and add the characters “//” (what’s between the quotes, don’t add the actual quotes), save the file, then reupload it to the server.
I managed to isolate the problem here. The issues happens when the AWeber Connect power-up in Leadin is enabled, which is conflicting with the AWeber functionality included in the Divi Elegant Themes. The conflict kicks in on the post editor and breaks the rendering of the editor page. Sorry we didn’t catch the issue sooner or before launching our AWeber power-up in Leadin – it’s really hard to anticipate every single problem that could arise with the tens of thousands of other plugins and themes that exist.
The good news is that we’ve coded a fix and should have it launched hopefully by the end of the week. We’ve run into a few problems with a popular AWeber PHP library we utilized to do our AWeber connection, but we shouldn’t cause anymore problems for you moving forward.
Thanks so much for reporting this one and I’ll make sure to post back here when we launch the new version of the plugin.
This could be a number of issues of the top of my head:
– Your theme may not call wp_footer anywhere in it, which means the Leadin tracking scripts wouldn’t be included
– Your pages might be cached
– Your form could be embedded via an iFrame which would block Leadin from hooking into the submission
– If there is a jQuery submit event attached to your form Leadin won’t be able to pick up the submissions your submit event overrides Leadin’s ability to hook into the submissionOnce I can sneak a peak at the source code I’ll take a deeper look for you. Do you mind sending me a link to your site with the form on it so I can take a look?
Sorry for the delay here. Can you send it to andy@leadin.com?
Thanks!
Forum: Reviews
In reply to: [HubSpot All-In-One Marketing - Forms, Popups, Live Chat] 'BUYER' Beware!!Thank you for the feedback, ginmi. We agree that the plugin is very resource intensive and is definitely not made for shared hosting environments, which realistically a huge portion of the WordPress market runs on.
For some backstory, when we initially launched Leadin, we focused on making something people love, and got to that goal quickly because we built Leadin on top of the core WordPress infrastructure. As time has gone on though, a few of our longer-term users are actually starting to run into problems where MySQL just isn’t scaling with the type of product Leadin is where we have to log every action a visitor takes.
Our goal is to bring inbound marketing software to the masses, and we realize keeping Leadin’s data in our user’s native MySQL just isn’t going to work long term, so we are actively working on a cloud-based version of Leadin that will store all your data on external servers to cut down on resource overheard. We know it’s a bit different than the standard WordPress plugin, but we’re trying to permanently fix the root of the issue while providing an amazing product. Are you interested in getting on the beta list for when we have that version ready for public use?
Cheers!
– AndyI totally understand. It’s not recommended to modify the source code but I understand it for dire circumstances.
There plugin’s tracking code is minified which makes it somewhat hard to read. Luckily because I helped write the code, I know exactly what you should edit to start collecting hidden input fields.
The file you’d want to edit is plugins/leadin/assets/js/build/leadin-tracking.min.js. All you need to do is remove the piece of jQuery in bold below that skips hidden elements:
$this.find(‘input[type!=”submit”], textarea’).not(‘input[type=”hidden”], input[type=”radio”], input[type=”password”]’).each(function(){…});
Becomes…
$this.find(‘input[type!=”submit”], textarea’).not(‘input[type=”radio”], input[type=”password”]’).each(function(){…});
Whenever you update the plugin you’ll need to keep making this change. Sorry I don’t have a permanent fix for you. One of the reasons Leadin is so easy to use is because we make opinionated decisions that cover the majority of use cases about how the plugin should operate to cut down on decisions for our users instead of adding a setting for every thing. Hope you understand.
Forum: Plugins
In reply to: [HubSpot All-In-One Marketing - Forms, Popups, Live Chat] Error warningHi Marilyn –
Sorry about the issue. We’re working on fixing these errors and should have a patch rolled out by the middle of the week. Thanks so much for letting us know.
Cheers,
– Andy