Whenever a translation job in the "Jumoo Translation Manager" is saved, an error occurs and this is the exception in the Umbraco Logs.:
{"@t":"2025-02-11T16:17:05.1979507Z","@mt":"Could not parse rich text editor value, see exception for details.","@l":"Error","@x":"Newtonsoft.Json.JsonReaderException: After parsing a value an unexpected character was encountered: \. Path 'opmaak', line 1, position 2625.\r\n at Newtonsoft.Json.JsonTextReader.ParsePostValue(Boolean ignoreComments)\r\n at Newtonsoft.Json.JsonTextReader.Read()\r\n at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject(Object newObject, JsonReader reader, JsonObjectContract contract, JsonProperty member, String id)\r\n at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)\r\n at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateValueInternal(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)\r\n at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)\r\n at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)\r\n at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)\r\n at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)\r\n at Umbraco.Cms.Core.PropertyEditors.RichTextPropertyEditorHelper.TryParseRichTextEditorValue(Object value, IJsonSerializer jsonSerializer, ILogger logger, RichTextEditorValue& richTextEditorValue)","@tr":"b42ab8df31384a1881de7f66592c8c48","@sp":"342a5c82771298f3","SourceContext":"Umbraco.Cms.Core.PropertyEditors.RichTextPropertyEditor.RichTextPropertyValueEditor","ActionId":"b10c416f-f9a4-4214-bf0b-56b15f14af7d","ActionName":"Jumoo.TranslationManager.Core.Controllers.TranslationJobApiController.Approve (Jumoo.TranslationManager.Core)","RequestId":"40000e64-0002-ec00-b63f-84710c7967bb","RequestPath":"/umbraco/backoffice/translationmanager/translationjobapi/Approve","ProcessId":5196,"ProcessName":"w3wp","ThreadId":101,"ApplicationId":"ea6c9907b5dfb977abd279e5dd977d85f29f78cb","MachineName":"wn1mdwk000BDU","Log4NetLevel":"ERROR","HttpRequestId":"9ff9d22f-09f2-4f22-817c-4c7b1a3e71d0","HttpRequestNumber":10925,"HttpSessionId":"9eb06820-38f4-0c77-ef64-7b88254cc144"}
You will need to use Translation Manager v13 with Umbraco v13, as it will contain updates for things like this (the internal format of how RTEs has changed a bit between umbraco versions).
Translation Job API exception
Whenever a translation job in the "Jumoo Translation Manager" is saved, an error occurs and this is the exception in the Umbraco Logs.:
{"@t":"2025-02-11T16:17:05.1979507Z","@mt":"Could not parse rich text editor value, see exception for details.","@l":"Error","@x":"Newtonsoft.Json.JsonReaderException: After parsing a value an unexpected character was encountered: \. Path 'opmaak', line 1, position 2625.\r\n at Newtonsoft.Json.JsonTextReader.ParsePostValue(Boolean ignoreComments)\r\n at Newtonsoft.Json.JsonTextReader.Read()\r\n at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject(Object newObject, JsonReader reader, JsonObjectContract contract, JsonProperty member, String id)\r\n at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)\r\n at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateValueInternal(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)\r\n at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)\r\n at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)\r\n at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)\r\n at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)\r\n at Umbraco.Cms.Core.PropertyEditors.RichTextPropertyEditorHelper.TryParseRichTextEditorValue(Object value, IJsonSerializer jsonSerializer, ILogger logger, RichTextEditorValue& richTextEditorValue)","@tr":"b42ab8df31384a1881de7f66592c8c48","@sp":"342a5c82771298f3","SourceContext":"Umbraco.Cms.Core.PropertyEditors.RichTextPropertyEditor.RichTextPropertyValueEditor","ActionId":"b10c416f-f9a4-4214-bf0b-56b15f14af7d","ActionName":"Jumoo.TranslationManager.Core.Controllers.TranslationJobApiController.Approve (Jumoo.TranslationManager.Core)","RequestId":"40000e64-0002-ec00-b63f-84710c7967bb","RequestPath":"/umbraco/backoffice/translationmanager/translationjobapi/Approve","ProcessId":5196,"ProcessName":"w3wp","ThreadId":101,"ApplicationId":"ea6c9907b5dfb977abd279e5dd977d85f29f78cb","MachineName":"wn1mdwk000BDU","Log4NetLevel":"ERROR","HttpRequestId":"9ff9d22f-09f2-4f22-817c-4c7b1a3e71d0","HttpRequestNumber":10925,"HttpSessionId":"9eb06820-38f4-0c77-ef64-7b88254cc144"}
What is causing this?
Hi Jonathan
Which versions of Umbraco and Translation Manager do you have installed?
Hi Kevin,
We are using Umbraco CMS version 13.5.2 and Translation Manager version 11.0.0.0
Hi Jonathan,
You will need to use Translation Manager v13 with Umbraco v13, as it will contain updates for things like this (the internal format of how RTEs has changed a bit between umbraco versions).
Kevin
Hi Kevin,
Thank you for your reply. We will arrange for Translation Manager to be upgraded.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.