Ability to choose which user to reassign content to

If it's always the same user you want to assign the content to, then you could edit in the module directly, in the function user_delete_submit() at line 145:

// reassign content
      db_query("UPDATE {node} SET uid = 0 WHERE uid = %d", $uid);
      db_query("UPDATE {comments} SET uid = 0 WHERE uid = %d", $uid);

Simply replaces uid = 0 by the user id of the one you want. 0 is the anonymous user.

If you want to select different users from a list, then changes to the modules are going to be too complicated for my skills, unfortunately.

Code has changed: this 2 lines no longer exist.
How can we now modify the reassigned user?

Any updates on this?

sub

Lets keep 6.x-1.x as it is and moving feature requests for 2.x branch, this way we can introduce features as additional module that can be ported to d7 also.

I did a patch for this issue for the 6.x-1.x- Branch. (Applied it against 1.3).
The patch is attached.

I'll try to implement this in the 2.x-branch as well, but as that branch seems not to be stable at the moment, we decided to patch 1.x instead. So for the moment I set this issue back to 1.x.

Oh, ok, modified the source and destination folders...

The above patch (#8) was applied to 6.x-1.x-dev.

And here is the 6.x-2.x-dev Version of the same functionality.

Hm... crazy... fixed line endings... should now work.

Thanks derhasi for working on this. I'll take a look to the 2.x patch and see if there are additional changes to include.

I applied the above patch and got an error when "Userpoints Nodes and Comments" is enabled:

Fatal error: Cannot use object of type stdClass as array in ...\sites\all\modules\userpoints_nc\userpoints_nc.module on line 246

I attached the module file where you can find this line - it belongs to a bigger function which may be important for you to see what happens there.

Best,
Tobias

@tobiberlin, I guess this is a problem in userpoints module, that tries to use a user-object that does not exist or is malformatted.

Besides:
I wrote a patch in addition to comment #8 (for 6.x-1 branch) to support reassign content AND unpublish it. I upload it here only for people who might be interested in the same functionality for v1.