Not sure what to tell you in this case. Do you have a cache plugin installed such as WP Super Cache or W3 Total Cache? If so, you should disable object and/or database cacheing or you will run into issues with registering users.
I have the same problem, after registration form is submitted, the page redirect to itself but response 404 error.
Here’s the page:
http://www.italvipla.com/offerte/
@ideazero – do you have any additional plugins (besides WP-Members) that also use reCAPTCHA?
Unfortunately no. The only plugin that uses reCAPTCHA is wp-member.
Maybe it could help you, I use “new user approve” plugin, in order to approve new users.
I’ve released 3.0.0.2 which includes a couple of fixes for reCAPTCHA, one of which is a problem with the file path for the included php library to make it work. If that file is not found (which it would not be in 3.0.0/3.0.0.1), then script execution would fail, so I think that’s the problem here. Please give that update a try and let me know if that helps.
This just happened on one of my sites, and I tested the form by only filling in one field at a time and was able to determine it was the Name field that I manually added. I unchecked it and displayed the native First and Last Name fields instead, and that solved the problem.
Yes, “name” as a field’s option name would do it. That is one of the many reserved terms in WordPress.
Here is a full list of terms you can’t use.
That explains it! Would it be possible to add some kind of error alert when you try to add a field that won’t work? Or even just a note at the top of the Fields tab with a link to that list that says, “you can’t use any of these fields.” Currently the top of that tab says, “Determine which fields will display and which are required. This includes all fields, both native WP fields and WP-Members custom fields.” Which, to me, indicates that you can use native WP fields.
Actually, a little while ago, I had added “name” to the error checking in the add form field process and was going to include it in an upcoming release. I changed that to check against the entire list of reserved terms and will include that update in 3.0.2.