"Language Overlay - How it works"
summary
Explains that TYPO3 implements overlays by loading the default record (language uid 0) then merging a translation row, replacing every field except uid and keeping the pointer in overlay_uid, enabling strict, fallback or free modes; versions use workspace id and version state so previews create extra rows rather than full copies. Recommends using PageRepository for correct language+workspace resolution. Recent work moves merging into the database with Common Table Expressions to reduce PHP hops while preserving sort order and many-language support.
AI-written summary · about
chapters (9)
- 0:00Introduction and talk overview
- 1:29What are overlays and their types
- 6:08Translation handling in TYPO3
- 14:46Language fallback modes explained
- 20:16Workspace handling basics
- 25:16Why TYPO3 uses overlays
- 31:48Database fields and API usage
- 37:54Writing data and edge cases
- 41:30Q&A and accessibility considerations
related talks
39mBuilding your translation process
38mDrupal 8's Multilingual APIs
45mTYPO3 Template Engine Integration Explained
27mWorking with Multilingual Data in SQL Databases through Erlang
46mDomain-Driven Design & TYPO3: The missing pieces
45mExtension Development with Extbase
37mMultilingualism makes better programmers - beyond PHP and JavaScript
55mPolyglot Persistence with Java
