Search by

young-dogs / typo3-ai-translator

youngdogs

Young Dogs AI Translation service integration for TYPO3

Package info

github.com/Young-dogs/typo3-ai-translator

Type:typo3-cms-extension

pkg:composer/young-dogs/typo3-ai-translator

Statistics

Installs: 6

Dependents: 0

Suggesters: 0

Stars: 0

Open Issues: 0

1.0.0 2026-11-19 21:55 UTC

This package is auto-updated.

Last update: 2026-11-20 11:48:51 UTC


README

TYPO3 backend extension that integrates the Young-dogs AI translation service into the standard TYPO3 localization workflow. When translating pages or content elements in the backend, editors can choose "Translate with Young-dogs AI" to have all text fields automatically translated in one go.

Requirements

Dependency Version
PHP 8.2 – 8.5
TYPO3 14.3

Installation

composer require young-dogs/typo3-ai-translator

Activate the extension via the TYPO3 Extension Manager or CLI:

./vendor/bin/typo3 extension:setup --extension=youngdogs_translate

Configuration

πŸš€ Need an API key? The Young-dogs AI translation service is available at young-dogs.com. Sign up to get your personal API endpoint URL and API key β€” no complex setup, just plug them in below and start translating.

Go to Admin Tools β†’ Settings β†’ Extension Configuration β†’ youngdogs_translate.

Setting Description
Translation Service URL Full endpoint URL of the AI translation API
API Key Secret key sent as X-API-Key header
Auto-enable after translation Sets hidden = 0 on all translated records (pages, content elements, inline children) immediately after translation
Disable "Translate to" prefix Removes the [Translate to Dutch:] prefix that TYPO3 normally prepends to header fields
Exclude fields Comma-separated fields to never translate. Use fieldname (global) or table.fieldname. Example: tx_bootstrappackage_header_class, tt_content.layout
Always translate these fields Comma-separated fields to force-translate, bypassing automatic detection. Use fieldname or table.fieldname. Example: pages.nav_title, tx_news_domain_model_news.keywords

API Contract

See Documentation/ApiContract.md for the full HTTP request/response specification.

How it works

The extension registers a TYPO3 14 localization handler (LocalizationHandlerInterface) which appears as a third option β€” alongside the standard Copy and Translate modes β€” in the localization wizard in both the Page Layout and Records modules.

When selected:

  1. All l10n_mode = prefixLangTitle fields (e.g. tt_content.header, tt_content.bodytext) are batch-fetched and translated in one API call per record before DataHandler::localize() runs.
  2. All other translatable input/text fields (e.g. inline children like bootstrap_package cards, news fields) are batch-translated per record in processDatamap_preProcessFieldArray.
  3. Fields listed in Always translate that are not normally part of the localization data map (e.g. pages.nav_title) are translated and written to the database after the record is created.
  4. The [Translate to Dutch:] prefix is stripped from all fields when that setting is enabled.
  5. Records are auto-enabled (hidden = 0) when that setting is enabled β€” applies to top-level records and inline children.

Supported record types

  • pages β€” page translations including fields in Always translate
  • tt_content β€” all content element types
  • Inline IRRE children β€” bootstrap_package cards, carousels, tabs, accordions, etc.
  • tx_news_domain_model_news and other third-party records (via Records module)
  • Any language-aware TYPO3 table

License

MIT β€” see LICENSE.

🌐 Connect with us

Β© 2026 Young-dogs Spain. Built with passion for innovation and operational excellence.