Translate: use prompt entities instead of custom configurations

Created on 28 September 2025, 12 days ago

Problem/Motivation

For historical reasons, ai_translate stores its prompts in a custom configuration (ai_translate.settings) together with other settings.

Switch to AiPrompt entities for storing default and per-language translation prompts would simplify settings schema, as well as the logic in AiSettingsForm and selecting correct prompt for selecting from language to language.

Proposed resolution

1. Use AiPrompts with predefined IDs (something like ai_translate-default, ai_translate.de.any, ai_translate.any.de, ai_translate.en.fr?)
2. Have only default prompt on module install.

Remaining tasks

1. Change the logic
2. Write update hook

Optional: Other details as applicable (e.g., User interface changes, API changes, Data model changes)

Marking as release blocker because suggested schema change affects contrib modules.

Feature request
Status

Active

Version

1.2

Component

AI Translate

Created by

🇧🇬Bulgaria valthebald Sofia

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Pipeline finished with Failed
    10 days ago
    Total: 223s
    #613611
  • Pipeline finished with Failed
    10 days ago
    Total: 340s
    #613644
  • Pipeline finished with Failed
    10 days ago
    Total: 339s
    #613668
  • Pipeline finished with Failed
    10 days ago
    Total: 238s
    #613757
  • Pipeline finished with Failed
    10 days ago
    Total: 300s
    #613789
  • Pipeline finished with Failed
    10 days ago
    Total: 214s
    #613801
  • Pipeline finished with Failed
    10 days ago
    Total: 196s
    #613829
  • Pipeline finished with Success
    10 days ago
    Total: 370s
    #613879
  • Pipeline finished with Success
    7 days ago
    Total: 229s
    #617101
  • Pipeline finished with Success
    7 days ago
    Total: 222s
    #617141
  • Pipeline finished with Success
    4 days ago
    Total: 239s
    #619588
Production build 0.71.5 2024