[Resolved] wpml editor deleting breaks, they have to be added in gutenberg afterwards

It turns out the developers have recently been working on this very issue and have proposed a fix, but that isn't scheduled for release until the WPML 4.7 update, and I'm not sure when that will be published (we have version 4.6.7 due very soon, which this fix was too late for).

My colleague did suggest a workaround, which you may want to try if you don't want to wait for the official release.

That is to edit the file wp-content/plugins/wpml-string-translation/classes/class-wpml-st-string.php and immediately after this line (line 243 of the current version)

			if ( ! empty( $translation_data ) ) {

insert these lines:

                if (isset($_REQUEST["action"]) && $_REQUEST["action"] == "wpml_save_job_ajax" && preg_match('/[\n\r]/', $translation_data["value"])) {
                    $translation_data["value"] = wpautop($translation_data["value"]);
                }

I need to look into this a little more, evidently.

When I tried the fix on the staging site it isn't working (though the fix that is included in WPML itself is not necessarily the same as the workaround offered by my colleague).

I'm off tomorrow, so it will likely be Monday before I have a reply for you, but I'll be in touch then.

On the sandbox test site my colleague updated the workaround. He removed that which was added previously described above, and added this to the theme's functions.php instead:

add_action('wpml_st_string_translation_before_save', function($translation_data){
	if (! empty( $translation_data ) && isset($_REQUEST["action"]) && $_REQUEST["action"] == "wpml_save_job_ajax" && preg_match('/[\n\r]/', $translation_data["value"])) {
		$translation_data["value"] = wpautop($translation_data["value"]);
	}

	return $translation_data;
});

What I then noticed while testing it is that it worked well if in the translation editor you are using the Text tab of the text editors, but it produced the double-paragraph problem if you used the Visual tab of the text editors, so I recommend using the Text tab.

To re-iterate, this just relates to a workaround for the problem. The actual solution which will be incorporated in WPML 4.7 is a different solution.