Drupal Customizable project naming convention
Requester:
Case:
Users don’t want every project created from Drupal to be auto-named like “Drupal TGMT…”. They need control over project names to match internal conventions and make projects easier to find (e.g., include node title, language codes, site name, date, etc.).
Possible solution:
  • Add a “Project name template” setting in the Drupal module (global and/or per-content basis).
  • Support tokens/placeholders like {site}, {node_title}, {source_lang}, {target_lang}, {date}, {user_prefix}.
  • Show a live preview and validate for length/forbidden characters; ensure uniqueness (auto-append counter if needed).
  • Fallback to current default when template is empty or invalid.
Acceptance criteria:
  • Admin can define and save a project name template; new Smartcat projects from Drupal use it consistently.
  • Names are unique, valid, and match the preview; invalid characters are stripped or replaced.
  • Backward compatibility: existing projects remain unchanged; turning the feature off restores the default naming.
Single multi-language project per Drupal nodeRequester:
Case:
When translating one Drupal post/node into multiple languages, the connector currently creates separate Smartcat projects per language. Users want a single Smartcat project containing all selected target languages for that post.
Possible solution:
  • Add an option “Group target languages into one project” in the send-to-translation flow (default can be configured).
  • Create one Smartcat project with multiple target languages and map each target back to the correct Drupal language variant.
  • Allow adding/removing languages later to the same project; handle re-runs/updates gracefully.
  • Sync per-language status/progress back to Drupal.
Acceptance criteria:
  • For a single source node with N target languages selected, exactly one Smartcat project is created with N targets.
  • Costs/progress/resources (TM/terminology) are shared within that project; statuses sync per language.
  • Subsequent additions/removals of target languages update the same project, not new ones.
  • Edge cases handled: cancellation of one language doesn’t cancel the whole project; retries don’t duplicate projects.
Auto-download translations to Drupal on workflow completionRequester:
Case:
Clients must manually click “Download translations” in Drupal. They want completed translations to be pulled into Drupal automatically when the Smartcat workflow reaches a chosen stage (e.g., “Completed” or “Published”).
Possible solution:
  • Provide a toggle “Auto-download on status” and let admins choose triggering stage(s).
  • Implement webhook listener (preferred) with polling fallback to fetch finished files per language.
  • Per-language handling: import as soon as each target reaches the trigger stage.
  • Include conflict resolution (skip/overwrite/create revision), error logging, and retry strategy.
Acceptance criteria:
  • When a project/target hits the configured Smartcat stage, the corresponding translation is imported to the correct Drupal entity/language without manual action.
  • Supports revisioning and configurable overwrite behavior; no duplicate imports.
  • Visible activity log with success/errors; admins can re-trigger imports safely.
  • Works with both single- and multi-language projects, and with updates after initial import.
Made on
Tilda