If you would prefer not to run SQL queries, which is part of the fix, I am not sure how else our team can help here.
Something else that you can try is to re-translate the bundled products - e.g. change them by making an edit, and re-send them to translation from the "WPML > Translation Management dashboard", and then re-translate.
In regards to the second reply, this issue might or might not be related to this other issue that we are currently handling in this ticket and our team asked if you can create a new ticket for this specific situation so that it will be escalated separately and investigated upon separately, so that we don't mix things and make wrong assumptions on the cause of the issue.
Our team found out that, for some reason, the issue was related to the "translation_item_id_of" meta key in the table: "woocommerce_bundled_itemmeta"
We depend on that table, and for some reason was pointing to incorrect IDs there.
Our team fixed this on the local testing environment they created by running the following code.
To get the bundled items IDs, they used the following query:
SELECT GROUP_CONCAT(`bundled_item_id`) AS test
FROM `wp_woocommerce_bundled_items`
WHERE `bundle_id` = '12660'
Which resulted in the values: "9377,9378,9379,9380,9381"
and then, to remove our keys that were pointing incorrectly, they used:
DELETE FROM `wp_woocommerce_bundled_itemmeta`
WHERE `bundled_item_id` IN (9377,9378,9379,9380,9381) AND `meta_key` LIKE '%translation_item_id_of%';
Then, they re-translated (saved the translation of the bundle product): /wp-admin/post.php?post=12660&action=edit&lang=en
However, this still does not fix the issue with the javascript and the fix is necessary yet again.
That should be fixed in a future update as the issue that you reported was escalated even further so that we don't only look for a workaround for the current situation, but actually fix it in a future update, too.
The fix that I shared above, again, requires some SQL queries and for the moment there is no way going around this, until this gets properly fixed by the dev team and deployed in one of the future updates.
The values are highly corrupted: we cannot have bundle with ID 9377 pointing to ID 7234 or similar, because that is invalid; especially since the original is with the higher ID.
That's the best that we can do at this point in regards to this issue.
I am currently setting the status of this ticket to "Escalated to WPML developers team" and once this issue will get resolved in a future update, I will get back to you in this ticket.
Unfortunately, there are no updates at the moment.
When exactly our developers will launch this fix is not up to us, the supporters, to decide, as there might be more urgent issues that have a bigger priority.
I hope that you will find this information helpful.
As I promised, when I will have an update, I will get right back to you.
