Get error when attempting to create a job even though there are multiple rich text editors in a grid control
Translation Manager Version: 8.2.9
I have a node I'm testing with that has grid content with a single rte. For some reason, translation manager is having trouble parsing the rte and so fails when creating a new job. Below is the grid content that fails.
<p><span class="blue-text medium-text">In this context, Personal Data is defined as information, both individually and if aggregated with other information, that allows the identification of an individual, either directly or indirectly.</span></p>
<h4><span class="blue-text">Information We Collect </span></h4>
<p><span class="blue-text medium-text">We collect the following categories of Personal Data about website visitors, candidates, marketing targets, and individuals registering for or using {client} services. </span></p>
<ul>
<li><span class="blue-text medium-text"><strong>System and device data:</strong> Internet Protocol (IP) address of devices, type of browser software, operating system, or mobile device in use, associated region or location data, Internet domain and service provider used, and referring/exit pages from which you linked to a {client} site</span></li>
<li><span class="blue-text medium-text"><strong>Job candidate data:</strong> Data provided by candidates in connection with employment opportunities</span><br /><span class="blue-text medium-text">Contact data: Name, title, organization, phone numbers, mailing address, and email address</span></li>
<li><span class="blue-text medium-text"><strong>Registration data:</strong> {client} information and marketing requests and event/seminar registrations</span></li>
<li><span class="blue-text medium-text"><strong>Marketing data:</strong> Participation in events and seminars, opt-in marketing selection, and document or resource download references</span></li>
<li><span class="blue-text medium-text"><strong>Customer data:</strong> Data received from customers in support of services provided to or on behalf of our customers</span><br /><span class="blue-text medium-text">Identification data: Government or national identifiers, identification documents such as passports or licenses, and dates of birth.</span></li>
</ul>
<h4><span class="blue-text">Personal Data Use </span></h4>
<p><span class="blue-text medium-text">The purposes for which we process Personal Data include the following: </span></p>
<ul>
<li><span class="blue-text medium-text"><strong>Enhancing our web sites</strong> requires us to use system and device data. Improving the use, layout, and content of our sites for our visitors is in our legitimate interests.</span></li>
<li><span class="blue-text medium-text"><strong>Protecting the security and availability of {client} information systems and assets</strong> requires the use of system and device data. It is in our legitimate interest to monitor our systems and assets to help detect and prevent misuse, tampering, or unauthorized access.</span></li>
<li><span class="blue-text medium-text"><strong>Considering candidates for job opportunities</strong> with {client} requires us to use job candidate data, contact data, and identification data for processing applications and complying with legal obligations which we are subject to</span></li>
<li><span class="blue-text medium-text"><strong>Addressing compliance and legal obligations</strong> require us to use contact data, identification data, customer data, and system and device data to ensure we comply with our legal obligations</span></li>
<li><span class="blue-text medium-text"><strong>Providing marketing information</strong> requires us to use contact data, marketing data, registration data, and system and device data. This includes newsletters, company announcements, conferences and networking opportunities, online resources, services, and {client} job opportunities. The processing of the data is in our legitimate interest in order to provide individuals who choose to opt-in for this information with tailored marketing information</span></li>
<li><span class="blue-text medium-text"><strong>Providing services and managing our relationships</strong> with our customers requires us to use contact data, registration data, and customer data in order to fulfill our contractual obligations to our customers and clients</span></li>
<li><span class="blue-text medium-text"><strong>Managing our business operations</strong> requires us to use contact data, registration data, customer data, marketing data and system and device data to support our contractual obligations and legal requirements for business processes including financial, resource, and supplier management.</span></li>
</ul>
<h4><span class="blue-text">Personal Data sharing</span><br /><span class="blue-text"></span></h4>
<p><span class="medium-text">We may share Personal Data with the following third parties:</span></p>
<ul>
<li><span class="medium-text"><strong>Suppliers or vendors</strong> in which we have a contract with to process Personal Data on behalf or at the direction of {client} for the processing purposes previously identified</span></li>
<li><span class="medium-text"><strong>Organizations involved in corporate transactions</strong> including any reorganization merger sale joint venture assignment transfer or other disposition of all or any portion of our business assets or stock (including in connection with any bankruptcy or similar proceedings); and</span></li>
</ul>
If I remove the last li of the ul at the end, it parses correctly. The strange thing is that I tried content with just the last ul, and translation manager parsed it correctly, so I'm unsure why it is failing.
Are you using the Microsoft Translation API Connector? I think we hitting a similar issue we had the other week with the v7 version. The provider only chunked the html at the top level and when that got bigger than the Microsoft request API, the split text was being rejected as not html.
Anyway., I have pushed out the updated v8 version of the Microsoft Connector, and this seems to have fixed this (for me). So an updated of this package should fix it:
Thanks for the quick response. I am using the microsoft translation api connector. Forgot to mention that. I updated to the latest version and confirmed that resolved the issue.
Get error when attempting to create a job even though there are multiple rich text editors in a grid control
Translation Manager Version: 8.2.9
I have a node I'm testing with that has grid content with a single rte. For some reason, translation manager is having trouble parsing the rte and so fails when creating a new job. Below is the grid content that fails.
If I remove the last li of the ul at the end, it parses correctly. The strange thing is that I tried content with just the last ul, and translation manager parsed it correctly, so I'm unsure why it is failing.
Any ideas?
Forgot to mention that it's running in trial mode, as I haven't purchased a license yet for this installation, in case that affects anything.
Hi Jesse,
Are you using the Microsoft Translation API Connector? I think we hitting a similar issue we had the other week with the v7 version. The provider only chunked the html at the top level and when that got bigger than the Microsoft request API, the split text was being rejected as not html.
Anyway., I have pushed out the updated v8 version of the Microsoft Connector, and this seems to have fixed this (for me). So an updated of this package should fix it:
https://www.nuget.org/packages/Jumoo.TranslationManager.Connector.Microsoft/8.0.3
Thanks for the quick response. I am using the microsoft translation api connector. Forgot to mention that. I updated to the latest version and confirmed that resolved the issue.
is working on a reply...