Hi bison_man –
Sorry about this issue and thanks for reporting it to us. The mixed content warning is actually a known bug that we’re rolling out a patch for in the next version, which is hopefully going live early next week. I’ll make sure to circle back here once we have the fix live in the plugin directory.
Thanks for the positive words too! It’s feedback like your’s that fuels our team to keep improving the product.
Cheers,
– Andy
I’m sure Andy’s team will get this sorted for you, but in the meantime, you could hard-code it into the plugin itself.
1. Locate leadin/inc/class-leadin.php
2. On line 52, comment out the code beginning wp_localize_script
3. Add the following just below it:
if(is_ssl()) {
wp_localize_script('leadin-tracking', 'li_ajax',
array('ajax_url' => 'https://{your domain name}/wp-admin/admin-ajax.php'));
} else {
wp_localize_script('leadin-tracking', 'li_ajax',
array('ajax_url' => 'http://{your domain name}/wp-admin/admin-ajax.php'));
}
Far from a proper fix (you should never normally edit plugins directly) it works well enough.
When Andy’s team updates the plugin, it’ll overwrite this hack with their (I’m sure) far more elegant solution.
Thanks Justin. That worked like a charm. I really appreciate it. And I learned something knew. Bonuses all over for a Friday!
@justin – thanks for the providing a temporary fix for bison_man – you rock!
We actually have a bug patch in place for this issue which will be included in the next version of the plugin rolling out this evening or early tomorrow.
Thanks for the patience guys and the ongoing support. We’re psyched to have you onboard.
We included a fix for this issue in Leadin 2.0.1.
I see you already marked this ticket as resolved, but I wanted to let you know anyways in case you wanted to upgrade to the latest version.
Thanks again for your patience!
