Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
- Created a service oriented architecture as per the Drupal standards.
- Removed duplicate code from module file.
- created service for export and import xlf file for a job.
- created a service to perform job related activity like import and update the latest status of job.
- Adjusted placeholder in messages, which was giving warnings due to PHP standards
- Apply PHP standard to all files exist in modules.
- Remove commented code to make it more readable and clean.
- Update date's time zone to UTC for status update logic.
- Resolve pending upgrade status related issue.
- Handle empty reference files related scenarios.
- Handled job status ambiguity exist on job listing page.
- Port connector to Drupal 10
- Handle issue for manual import.
- Remove errors occurred on logs which are available on job's detail page.
- Corrected behavior when 'Transfer all files as zip' is enabled.
- Corrected behavior when 'Use one export file for all items in job' is unchecked
Fix: Jobs not importing due to prev and current job statuses being the same when the job status get updated, resulting on the ack being closed without download the translations
Autoimport fix, jobs not importing when details are opened before CRON runs.
- When Autoimport is ON: Cron is expected to import automatically, if there is a need to rush the import, and the translation is ready, the user can click the Import button from the job details screen.
- When Autoimport is OFF: The user is expected to click the Import button when the translation is ready.
Issues fixed:
-Missing Content API V1 parameters handlers added on existing jobs
-Warning messages in the logs reporting missing Content API V1 credentials when existing jobs are unable to retrieve their state
-Fixed issue related to the inability to complete for jobs created using previous versions of the connector and not updating correctly while running CRON
Fixed issues related to:
- Accepted jobs re-delivering translations
- Wrong provider credentials storing
- White screen of death on provider setup
Notes: If the connector presents "Invalid ClientId" job warning logs, it's required to go back to the provider settings and make sure they are valid by clicking save before continuing seonding jobs
Bug fixes:
- Connector not updating the status for every job
- Connector reverting statuses of already finished jobs
- Reduced amount of logs
- Removed setting a higher than default value for Max Execution Time for PHP
- Jobs created with providers other than Lionbridge are created and works as expected
Dev have released build 2.12 that solves the functional issue where a translation job doesn't get imported to Drupal during cron when you have the "Auto import job" setting enabled.
-CRON flow refactored to pull only jobs with status changes instead of scanning all open jobs
-Issue about continious revisions being created on every scan has been fixed
-Dates format simplified
-Update TM feature re-activated
-Content Api V2 Endpoint is now configurable through the settings screen
-Issues with jobs not finising fixed
-Issues with getting status from Content Api V1 fixed
-File opener properties updated to latest standard
As part of Lionbridge commitment on continuous improving the quality of the digital services. This module offers backward compatibility with the credentials and connectivity to the legacy Lionbridge Translation Services supported on the previous module Lionbridge translation provider (legacy)
As part of Lionbridge commitment on continuous improving the quality of the digital services. This module offers backward compatibility with the credentials and connectivity to the legacy Lionbridge Translation Services supported on the previous module Lionbridge translation provider (legacy)
You can now migrate from version 1.x of the Connector, which supported only the Lionbridge onDemand translation provider, to the current Connector version.
To migrate from versions 2.0-2.3 of the Connector to the current Connector version, you must complete the processing of all jobs in the older version, uninstall that version, and delete the corresponding folder from the server before installing the current Connector version.
TM Update feature adjustments:
- use batches for packaging TM job items in files to avoid endpoint throttling issues
- XML files will store max 500 items per file