Andy Cook

I just wanted to follow up here to see if you were able to debug the 500 server issues to any of the issues above. Thanks for letting me know in advance. Figuring out the root cause of bugs helps us make the plugin better for every one using it.

@dantesama – Can you please post the URL of your site or email support@leadin.com with your domain so we can take a closer look?

I’m working with bopjo1 already to figure out what’s going here and having two sites to check for patterns will be really helpful in debugging the issue.

Thanks!

Hi Jeff –

I just wanted to quickly check in with you on this to see if you were ever able to get Leadin working on your website by trying out the two solutions I proposed.

Thanks,
– Andy

Hi –

First off, so sorry for the issues. We work really hard to make sure Leadin isn’t buggy, but we definitely do miss issues with the near infinite combinations of PHP, WordPress, MySQL, themes and plugins.

Are you able to access your error logs to see what the cause of the problem might be? Off the top of my head, it could be a number of things:

1. Leadin 3.1.5 had an issue with the allow_url_fopen setting in php.ini where we didn’t have a test to see if that feature was enabled, so it’d throw a PHP error. We fixed this in Leadin 3.1.6, but it’s possible that your WordPress updater is throwing an error from the upgrade to 3.1.5 to 3.1.6 and breaking in the process because the headers are already sent. The solution would be to deactivate the old version of the plugin, then run the upgrade to 3.1.6.

2. Leadin is a resource heavy plugin, and occasionally will hit the WP_MEMORY_LIMIT threshold if it’s not set high enough on your server. We’re working on mitigating this issue permanently, but for now you might want to try increasing the amount of memory limit available to WordPress in your wp-config file. Can you try adding the below line to your wp-config.php file to see if that’s the issue:

define( 'WP_MEMORY_LIMIT', '256M' );

Let me know if neither of those fixes work and we’ll try to go from there. It’s really hard for us to figure out what the cause might be if we don’t have server access, so if you want to send me over FTP access to your server I’m more than happy look for the cause to the problem.

Hi Scott –

I completely understand and thanks for taking the time to circle back here with your feedback.

We recently added four amazing engineers to our team, and they are working hard to rewrite most of the plugin right now to nix the issues you experienced, and even head off a few more that you avoid but other people are experiencing.

I can say our small team is working as fast as possible to build the most powerful, easy to use product for Inbound marketing. We’re improving every day, and feedback like yours is extremely valuable in helping us figure out what we need to do a better job with. Thanks so much and I hope you’re able to check out Leadin again sometime in the near future once we fix these issues.

– Andy

Hi Jaun –

I wanted to follow up that we recently started sending through all your email notifications through an email delivery service, so if you upgrade to Leadin Pro you should start receiving your email notifications. The reason we made this change is that we found the default PHP mail server just wasn’t reliable enough or often was marked as spammed, so we decided to give away a better email delivery service for free. Thanks again for letting us know about this issue and if you update to the latest version of Leadin your notifications should start working.

Cheers,
– Andy

I wanted to just follow-up that our team is going to start working on adding in a timed-popup feature soon. Keep on the lookout for that update and if you aren’t already subscribed, you should hop on our product updates mailing list to make sure you don’t miss it:

http://leadin.com/dev-updates