Not sure how it's happening for a new user though. Are you displaying any of the params fields (e.g. language, editor, etc..) during registration?
Kyle (Krileon) Community Builder Team Member Before posting on forums:
Read FAQ thoroughly
+
Read our Documentation
+
Search the forums CB links:
Documentation
-
Localization
-
CB Quickstart
-
CB Paid Subscriptions
-
Add-Ons
-
Forge
-- If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
-- If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please
send me a private message
with your thread and will reply when possible!
-- Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
-- My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.
Thanks for posting that reference to the other ticket.
Although I agree that it isn't completely 'logical' that existing data in the params field would cause a problem, we did have a 'different' user-manager extension installed on this site and it looks like it must have messed up the params area.
We just used the query to replace all the params with "{}" (which is fine, because we don't allow users to change those), and it's all working properly now.