Andy Cook
Forum Replies Created
-
Hi Steve –
I just wanted to reach back out to you one last time to see what version of WordPress you’re running on http://www.prepaidfuneralreview.co.uk?
Thanks!
Do you mind emailing me a link to your website?
Also, what versions of Leadin and WordPress are you running? It sounds like one your Leadin MySQL queries might be breaking, and this could be caused by a bug we recently fixed in Leadin 2.2.10 for old versions of WordPress lower than 4.0.
It’d help me debug this a lot faster too if you could create an administrative login to your WordPress dashboard for andy@leadin.com. I’m happy to take a look for you to get to the bottom of this issue.
If you drop this bit of code into your functions.php file the Leadin nav menu item should disappear for all user roles:
function hide_leadin_nav () { echo ' <style type="text/css"> #wp-admin-bar-leadin-admin-menu{display: none;} </style> '; } add_action( 'wp_print_styles', 'hide_leadin_nav' ); add_action( 'admin_print_styles', 'hide_leadin_nav' );Right now the Leadin popup is not configured to run on mobile devices. This is because we got a lot of complaints from our early users around a sub optimal experience on mobile devices using the default responsive design, so in the essence of speed we just disable the mobile popup saying to ourselves “we’ll fix it when we have more time”, but we never have more time so we didn’t get around to it.
We’re hoping to take care of this one soon and thanks for letting us know that you want the popup form to show on mobile devices. For now I’ve added you to the list of people interested in this feature on our backlog and I’ll circle back with you once we make the edit to the plugin behavior to show the popup on mobile browsers.
Cheers!
Awesome – glad you were able to see it in action and hope you can get it working on LSMGuide too.
tl;dr – I agree with your points and I’ve added MailChimp groups support to our backlog of features to explore.
I’m posting the response I sent you via our support desk so other’s can view it here:
Hi Manuel –
So the reason we’re not using MailChimp Groups right now is that none of the other email services are set up this way and we honestly just didn’t know how MailChimp handled groups when we first built the integrations. It is a good point though and I’ll look into figuring out a way we can fix it while still supporting the other email service providers that our customers are using already. You’re actually not the first person to request MailChimp Groups integration and I’m sure you won’t be the last, so I give you my word I’ll look into figuring out how we can make this work the next day I get some free time to dig into the code. I’ll circle back with you as I make progress on figuring it out and will keep you posted.
Thanks!
Hi Paul –
I’ve isolated this issue to the validation library provided by MailChimp – http://s3.amazonaws.com/downloads.mailchimp.com/js/mc-validate.js
Which is included in the source code for the pages like so:
<p><script type='text/javascript' src='//s3.amazonaws.com/downloads.mailchimp.com/js/mc-validate.js'></script><script type='text/javascript'>(function($) {window.fnames = new Array(); window.ftypes = new Array();fnames[0]='EMAIL';ftypes[0]='email';fnames[1]='FNAME';ftypes[1]='text';fnames[2]='LNAME';ftypes[2]='text';fnames[3]='MMERGE3';ftypes[3]='text';fnames[4]='SOURCE';ftypes[4]='text';}(jQuery));var $mcj = jQuery.noConflict(true);</script><br /> <!--End mc_embed_signup--></p>I can’t get to the exact root of the problem here because that code is minified (which makes it really hard to read), but my deduction is that script is submitting the form via ajax using the function ajaxSubmit. Unfortunately Leadin can’t detect ajax form submissions. One quick solution to the fix is just remove the above code from your embedded form and Leadin should start catching all the form submission. If you don’t enable their ajax submission though the submission will open up a new tab, which isn’t the best.
An alternative solution is that you can recreate your forms using one of Leadin’s supported form plugins and then setup a MailChimp connect list to push your contacts into your MailChimp account. That way you’ll get the best of both worlds.
I don’t think we’re going to be able to figure out how to support ajax forms by default, so I’m going to mark this ticket as resolved and hopefully you can use one of the options that’ll work with Leadin.
Sorry for the delay here, Paul.
If it helps… I also tried to get the built-in sign-up forms to work… pop-up, top, bottom – with no luck.
I tested it in “incognito” as well as in other browsers…
I took a look at your source code and the Leadin code to make the popup work doesn’t seem like it’s being included. Do you have a caching plugin enabled? If you do, try clearing your cache and then refresh the contact us form.
As for the embedded form, I’m adding a MailChimp embedded form to my blog and am testing it on my site. Hopefully the behavior is similar to so I can debug it on my own servers. I’ll post back what I can find in a few minutes. Thanks for your patience. We really do appreciate it.
Leadin will scoop the form submission and create a contact in your database for you. We automatically spin up a “Subscribers” list when you activate the Popup-form Power-up, but you can hook modify that content of that form and hook it up to any tagged list you’d like using the CSS selector “.vex-dialog-form”.
If you setup a connected email list to one of the third-party email integrations, Leadin will also push that contact to your external email tool.
Hopefully that answers your questions and let me know if you need to know anything else about what happens. Cheers!
Forum: Plugins
In reply to: [HubSpot All-In-One Marketing - Forms, Popups, Live Chat] Aweber errorHi Scott –
Thanks for the printout of the error logs. This is a known bug that I’m hoping to take care of this week. Basically the issue here is that you have two plugins trying to include an AWeber library with the same class name. Typically we’d just be able to namespace our service under the Leadin logic, but because so many of our users run PHP 5.2, we can’t use namespaces. They didn’t exist until PHP 5.3 unfortunately.
I’ll circle back with you once we have this fixed and launched.
Hi Steve – I may have figured out what’s going on here. Do you happen to be using and older version of WordPress < 4.0?
We’re working on some major changes in the next few months which will hopefully finally allow us to integrate with Zapier, so eventually you should just be able to use Leadin to setup the push into Base CRM.
Right now we can’t pull it off technically because we’d have to create an endpoint for every single WordPress site, which is impossible.
Leadin attaches a unique tracking code to each visitor, so what happened here is you visited the site, got a tracking code then you submitted the form with Email Address A.
Later on you revisited the site with the same tracking code because it was the same browser session, then submitted a form with Email Address B. Since you were using the same browser session (therefore the same tracking code), Leadin updated your Email Address to Email Address B because technically you’re the same person, but you’re just using two different email addresses.
Only having one email address is a legacy constraint from the original version of the plugin, but we’re working on figuring out how to attach multiple email addresses to the same contact.
Thanks for the question and let me know if you want more clarification around how the tracking algorithms work.
There goes my theory…
So it looks like there’s an admin-ajax.php error happening, which usually indicates there’s a PHP error on the server when it’s hitting the ajax file. I pointed it out in this screenshot of the Javascript console for your site:
https://leadin.com/wp-content/uploads/2015/01/Screen-Shot-2015-01-22-at-5.45.18-PM.png
This is an issue we run into from time to time because of the very nature of WordPress. If another plugin has a PHP error in it, it’ll break out ability to track activity in the data base. Unfortunately the only way for me to really get to the bottom of this on your specific server configuration is if you send me FTP access to the server and create me an administrative WordPress login to your site so I can verify that the fix is actually working once I figure out what’s going on. Sorry I don’t have a better solution… not being able to control the server environment and access the error logs is one of the major downsides for us WordPress plugin developers… Hope you understand.
My email is andy@leadin.com. If you send over that information I can try to figure out what the root of the cause is tomorrow for you.
Thanks!
Sorry for the delay here. We’re doing our very best to keep up with support tickets, but between answering everyone’s inquiries and actually fixing bugs then deploying the fixes, we’re admittedly not operating as fast as we’d like.
Based off your Javascript console I think what this is causing the issue here I found yesterday with versions of WordPress < 4.0.
Do you happen to be running an older version of WordPress?
