last two versiona are causing 500 error

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.