Releases for Lionbridge translation provider

- Added support for PHP 8.4
- “Purge finished” will also remove eligible records from the tmgmt_capi_request_processor table.

- Improved reliability in multi-container deployments by resolving an inconsistent array issue and storing file metadata in the database as a single source of truth.
- After job creation, only the ZIP file is retained on the server; all individual XLF files are automatically removed to optimize storage usage.
- Fixed an issue where the job state was not updated correctly during redelivery; the job now transitions to the Active state as expected.

- Database Schema Enhancement: Added three new tracking columns (file_upload_status, file_upload_attempts, capi_response) to the tmgmt_capi_request_processor table for comprehensive job monitoring and error tracking throughout the translation lifecycle.
- Improved Job Submission Logic: Redesigned job submission workflow to handle single-file scenarios more efficiently, ensuring consistent queue processing and eliminating submission failures for edge cases involving individual file uploads.

- Fix analysis code (AC) where no configuration — no API calls will be made
- Due date validation — convert to string if returned in array
- Remove deprecated code related to reference field
- Trim error message up to 200 characters
- Titles sanitization during job submit
- Status discrepancy on Job Overview page
- Errors encountered while re-delivering single-file ZIP job

- Introduce a queue for XLF and ZIP file generation.
- Update the Translation Memory (TM) to accommodate the newly introduced queue.
- Update the cleanup process in case of job failure to remove items from the newly added queue.
- Added more logs in case of cleanup process on job failure.

- Updated ZIP import processing to use the queue during auto-import (consistent with manual ZIP handling).
- Fixed duplicate job creation and improved job cleanup after job post failure.
- Added code to create a template processor view.
- Added permission for the queue controller processor.

- Implemented a queue for data migration.
- Implemented a queue for manual import via a ZIP file.
- Implemented multiple queues for sending jobs to the provider to avoid timeouts and submit data in chunks.
- Enabled the cron option in the queue worker to process the queue during each cron execution.
- Displayed job submission status ("In Submission Queue").
- Removed the shell script used to trigger the queue.
- Implemented a controller to trigger queue processing.

- Fixed an issue where importing jobs from a ZIP file caused an exception due to multiple attempts to close the ZIP file. The second attempt resulted in an exception, preventing jobs from being processed.
- Resolved a bug where users were unable to select the "Quote" option when attempting to send a job.

Implements a failsafe import mechanism on cron and manual import.

- Improved token management to avoid redundant token generation.
- Enhanced synchronization: Prevents job deletion from CAPI when deleted from Drupal.
- Provider optimization: Prevents multiple TMGMT Lionbridge provider creation.
- Streamlined provider configuration flow on the edit form.

-CRON process refactored to update deliveries using queues. This prevents execution timeouts that would otherwise abort heavy lifting delivery runs

- 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.

- 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

- Added support for PHP 8.1
- Fixed bug on the Xliff parser when adding multiple node types within the same job

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

-Fix: Issue in autoimport, when running the jobs fix procedure with wrong credentials or endpoint

Fix missing Job instance while manual Importing

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

-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

Dual connectivity

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)

What's New?

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.

Issues Fixed in This Release

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

New features:

• Translation Memory Update
• Redelivery of completed jobs

Bug fixes. New features.