I can pretty definitively say that this is an issue with the fopen settings on people's servers. I am going to roll out a version 3.1.1 to give two mitigations and some diagnostics on this issue.
I've already emailed CuChulla1nn, but here are the checks to perform for anyone else who experiences this
Add or uncomment out these top two lines on register.php (they're included in version 3.1.1 and beyond)
Code:
error_reporting(E_ALL);
Code:
ini_set('display_errors', 1);
Try to register again, and the error will pop up in the header of the site. It will most likely say something about fopen (which is required by reCAPTCHA). Different servers handle this differently, which is where the problem comes in. Some servers can be fixed by adding the following line to the top of login.php and register.php (which was added in 3.1, I believe), but older versions don't have it:
right above the require_once
Code:
ini_set("allow_url_fopen", 1);
BUT, some servers don't seem to be respecting that, so the next step is to add a php.ini file wherever you installed UserSpice (this will be included in 3.1.1 and later). The PHP ini should just say:
Code:
allow_url_fopen = on
If that doesn't work, you're going to have to talk to your hosting provider or dig through your php.ini file for the server to enable url_fopen.
I hope that helps, and thanks to all of you who didn't just dump the software but decided to press on and help the entire community find a fix for this problem.