Attempted merge results in AJAX error and terms do not merge

Subscribing:

An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /batch?render=overlay&id=193&op=do StatusText: Service unavailable (with message) ResponseText: Recoverable fatal error: Object of class stdClass could not be converted to string in _term_merge_insert_field_values() (line 469 of /home/sites/shared/sitename/live/site/modules/term_merge/term_merge.module).

Closing the overlay reveals a system message saying the terms are merged, but alas they have not been.

subscribe. I Have the exact same problem

I get the same error

An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /batch?id=441&op=do StatusText: error ResponseText: Recoverable fatal error: Object of class stdClass could not be converted to string in _term_merge_insert_field_values() (line 469 of /home/betacssd/public_html/sites/all/modules/term_merge/term_merge.module).

I have moved this up to a major bug as the module is useless otherwise.

Hi guys,

I can provide a patch for this later, but essentially it's the fact that any references to $update_data_arr['dest_tid'] are wrong, as it's an object not a string.

So on lines, 449, 460, 469 -

$update_data_arr['dest_tid']

Should be -

$update_data_arr['dest_tid']->tid

The error only occurs initially because the object is trying to be used as a string in the output (as it says in the error). If you just fix line 469, it will error again for the database update because on line 449 the TID is being set with the object and not the string of $update_data_arr['dest_tid']->tid.

With the three simple fixes this got the module working again for us. As I said when I get time I can post a patch.

Thanks,
luke

Thanks luke for finding the problem.
I created a patch with your changes. It works fine for me now.

Its better to change one line in function term_merge
Line 348
'dest_tid' => $dest
to
'dest_tid' => $dest -> tid,

Thanks fixed!

thanks for the patch!

This fixed my issue. Marking as "reviewed and tested", as it has proven to work for several of us.

Confirmed: patch fixes it for me.

Patch committed in the last dev version and upcoming beta-2, thank you very much and sorry for my inactivity!