[Closed] Fatal error when using WPML Multilingual CMS & WPML String Translation combined

Ok, after hours and hours of trying everything I could think of I found the solution.
I want to share it so that other people don't have to go through the same trouble as I did.

Previously I developed a fully custom product page, fully coded by myself so I had full freedom in every aspect.

I used php, html, js(jquery) and css to achieve this.
After some time I've downloaded the WPML Language/Currency plugin to be able to easily switch between currencies on my website.

Because my shop page is completely custom I had to incorporate the WPML logic into my code so it would react to currency changes made by the user.
It took me a while to get this to work, but eventually I used this line to include the WPML logic into my script:
do_action('wpml_before_init');

This enabled me to use code to get the product prices in the currency selected by the user:
// Product Price
//Conversion
$regular_price = apply_filters('wcml_raw_price_amount', $product->get_regular_price());
$sale_price = apply_filters('wcml_raw_price_amount', $product->get_sale_price());
// Retrieve the current currency
$currency = isset($woocommerce_wpml->multi_currency) ? $woocommerce_wpml->multi_currency->get_client_currency() : get_woocommerce_currency();
// Format prices based on the current currency, ensuring currency code is included
$formatted_regular_price = wc_price($regular_price, array('currency' => $currency));
$formatted_sale_price = wc_price($sale_price, array('currency' => $currency));

Before I activated the plugins needed for the translation part of WPML to be usable I had to include the WPML logic with do_action('wpml_before_init');

After activating both plugins:
- WPML Multilingual CMS
- WPML String Translation

The inclusion of do_action('wpml_before_init'); caused some logic to be included twice, so my website generated a Critical error until I would deactivate one of the two plugins mentioned above.

I hope this will help other people in the future, but above all, I think the plugin developers can use this information to make some changes to the plugin code, preventing this from happening in the future.
I think there can be a relatively simple solution to make sure that this situation won't occur for other users in the future.

I look forward to work with the translation functionality you provide.

One last thing.. The plugin used up a lot of my translation credits in the time it wasn't working properly.
So now I have lost more than half of the credits dispite it hasn't been able to save the translations properly on my website.
Is there any way I can get compensated for the loss in translation credits?

I wrote a detailed error report and solution, so I hope that in turn you can help me by refunding the credits lost during this process.

Before you ask, the translations ARE published.
I selected the option to publish all translations and also mark them for review.

Dispite being published, the only part of my website being translated is the menu in my header.

Like i mentiond above, I would like to have a refund in translation credits so I can start over fresh.

The plugin list I provided in my first post was the situation where my site kept crashing when I installed and activated the string translation plugin, so that's the reasin why it wasn't on the list. In the current situation I have installed this plugin together with the wpml multilanguage cms. I can see the translations on most of the pages when i look under WPML->string translations, but when I go to the actual page on my website and switch to anothe language, the only thing that's being translated is my header menu.

I tried following these steps, but at step 1 I already get different results than expected.
Please look at the image to see what the problem is.

It won't delete everything from the languages.
Tried multiple times but no success.
My browser console generates some errors after a little while, errors are the same for each language when i try to delete them:
Uncaught (in promise) SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data
n hidden link
l hidden link
(Async: promise callback)
n hidden link
u hidden link
exports hidden link
exports hidden link
j hidden link
Z hidden link
u hidden link
p hidden link
y hidden link
y hidden link
it hidden link
at hidden link
ut hidden link
pt hidden link
L hidden link
V hidden link
Jt hidden link
Xt hidden link
unstable_runWithPriority hidden link
$a hidden link
I hidden link
Yt hidden link

Should I proceed to step 2 regardless?

I see that all html tags and such get removed from the comment text, and only plain text remains.

The error occurs on a h4 element on top of the snippet.
It looks like it is the html used to show the modal that pops up when you click the delete button with the cross inside, right of the language you want to delete.
When i click the "Yes, delete all "language_name" translations" button, the error comes up after some seconds..