I pm'd you with the login but the problem is that in J1.6 with CB 1.4 your params are in a json string like format and your parse function in cbParamsBase can't deal with that. It trys to split on \n which doesn't exist in the new params object.

{"moduleclass_sfx":"","horizontal":"0","compact":"0","pretext":"","posttext":"","logoutpretext":"","logoutposttext":"","login":"","logout":"index.php","show_lostpass":"1","show_newaccount":"1","show_username_pass_icons":"0","name_lenght":"14","pass_lenght":"14","show_buttons_icons":"0","show_remind_register_icons":"0","login_message":"0","logout_message":"0","remember_enabled":"1","greeting":"1","name":"0","show_avatar":"0","avatar_position":"default","text_show_profile":"","text_edit_profile":"","pms_type":"0","show_pms":"0","show_connection_notifications":"0","https_post":"0","cb_plugins":"1"}"

If you want I have written a fix for this. Thank you - Trip

Apparently I can't paste code into this forum so my ten minute disertation was just blown away.

comprofiler.html.php loginForm() causes module params to load as JSON string into raw_params. When that is passed to cbParamsBase .... cbParamsBase has a parse function that can't deal with the JSON.

I modified the parse function to deal with JSON in the string and added an objectToArray function to get the params object back to a good array the rest of your code can deal with.

Can you please comment on your position with regard to this bug? I need to know how I am going to deal with it in current and future projects.

Thank you,

Trip