I am encoutering this error when I have this module activated and it is not allowing someone to signup on the site

I believe this is fixed in the dev release. Would you mind trying that?

I did a release of 6.x-2.3 that includes recent work. You can try that as well.

I suspect that this error is not preventing your signups, but is a side-effect of another problem.

I would imagine it's the same issue. Please say what version you're running now, and what other modules you're working with.

I imagine you're using profile module with a telephone number or something? What kinds of fields are you using in profile if that's the case?

OK. I imagine that you have a profile field that has multiple parts. If you could please at least give a screenshot of all your profile fields that would be appreciated. May need a database from you. If you can make that available it would help. You could put it in a dropbox or whatever.

I can't guarantee when I can work on this as I've been pretty backlogged and have some critical stuff elsewhere.

Thanks. OK, please do email the database or throw it in a dropbox. randy at randyfay.com. I can't guarantee when I'll work on it. Recent versions of drush have a database sanitizer if you have user information in there you'd like to get rid of. (in a copy!)

Thought we had this solved already.

Same here, using role Delegation, subscribing.

I'm unable to recreate any of these issues using the current dev. I tried triggers, tried role delegation module. Did everything I could think of./

Somebody is going to have to send me a database. randy at randyfay dot com

I began experiencing this same issue "array_merge() [function.array-merge]: Argument #1 is not an array in /var/www/vhosts/newsite/httpdocs/modules/role_change_notify/role_change_notify.module on line 122." I started happening when I updated core and a number of modules on a site that was rather out of date. Prior to these updates, the site was using 6.x-2.x-dev. Once I did the updates, people started getting WSOD and that error on registration. The users were actually getting added to the database, but not with the proper settings. They were not supposed to be automatically approved, yet they could log in. I had to go all the way back to 6.x-1.2 to get it working again. That is where things stand now.

This site is using Drupal core 6.22, logintoboggan 6.x-1.9, profile_checkboxes 6.x-2.0, RoleAssign 6.x-1.0-beta3, Profile Location 6.x-1.2 and Profile CSV 6.x-1.1. I'm afraid I can't send the database since it contains all kinds of private user data and our client will not allow it. Let me know if there is any more information I can provide that will help. Thank you

@nrackleff, the last change to 6.x-2.x was on January 25, 2011. 6.x-2.3 and 6.x-2.x-dev are the same thing... Since Role Change Notify reacts to user_save() events, it's possible that some module is passing unexpected data in.

I updated core and 20 modules that day. I may try rolling back each one at a time and see which one "unbreaks" it. Something in the updates also seems to have caused a problem with tokens not be replaced in an email that is set up as an action. I'll keep poking around. I'll let you know if I find out anything.

I would consider debugging this if you are willing to give me me a tarball of your site and a dump (sanitize it if you want) of your database. You could dropbox them to randy at randyfay dot com or use any other technique you want.

Thanks so much for offering to help. I will see if I can get permission to send you the site and database if I clear out the user data and ubercart orders and things like that. Since my last post, I updated the token module and found that the tokenized email that wasn't getting sent properly had an invalid token in it. Once I replaced that invalid token, the email started working properly. After that, I tried to upgrade Role Change Notify again, but it didn't work and went back to WSOD upon registration. I will let you know if I can send you the files. Thanks again for the offer.