Tags give the ability to mark specific points in history as being important
-
1.0.3
2cbe5b88 · ·This release adds a settings page to exclude content from the untranslated-content search, a Lionbridge submit command that can resend jobs, a command to assign providers, links from job items to their source content, and several Lionbridge fixes. New features Exclusion settings page: at Administration » Translation » Settings » Drush helper (/admin/tmgmt/settings/drush-helper), you can exclude whole entity types or single bundles. Excluded content is left out of tmgmt:scan-untranslated and tmgmt:job-batch-add --missing-only, including referenced terms and blocks. It can still be queued without --missing-only. New tmgmt:job-submit-lionbridge command (tmgmt_helper_contentapi): submits jobs with their Lionbridge settings. These are provider, due date, PO reference, description, quote, analysis codes and export format. New --resubmit option for jobs Lionbridge never received. It: deletes the earlier Lionbridge job; resets the connector's upload records and queue items; submits the job again. It asks for confirmation, and --dry-run shows what it would delete. New tmgmt:job-update command (alias tmgmt-ju): assigns a provider and its settings to jobs that have not been submitted. --without-provider finds jobs whose provider is missing, deleted or disabled. LionBridge Job ID column on the jobs overview (/admin/tmgmt/jobs), when tmgmt_helper_contentapi is enabled. Links to source content: job item labels on a job's page link to the node, term, media item, block or webform being translated, if it still exists and you can view it. You can turn this off per view in the "Label" field settings. tmgmt:job-submit-all handles providers that send jobs in the background (reported as "waiting for the provider"). It also skips Lionbridge jobs that lack their Lionbridge settings, because the connector would silently ignore them. Bug fixes Deleting a job, with Drush or in the UI, now removes it from the Lionbridge send queues. Before, a leftover queue item stopped cron with a fatal error. Jobs containing interface strings are no longer sent to Lionbridge, whose connector cannot export them and fails in its queue. tmgmt:job-batch-add now keeps content, config and interface strings in separate jobs. Assorted fixes to unit and kernel tests. Code quality and security The code passes PHPStan level 5, with a phpstan.neon used by GitLab CI, and the Drupal and DrupalPractice coding standards. The code was reviewed against Drupal's secure coding guidelines. Job item source links now carry the cache data of the access check, so a cached view cannot show links to users who cannot open them. Upgrade notes Run drush updb to add the LionBridge Job ID column to the jobs overview on sites where tmgmt_helper_contentapi is already enabled. Run drush cr so the new settings page and its tab appear. No exclusions are set by default, so the commands behave as before until you configure some.