Files
VITEC-website/packages/vitec/Resources/Private/Language/locallang_pages.xlf
o-rasche 409afc2433 VITEC headless: ContentElementResolver, Product fields (videofile, showdatapath)
- New Classes/Service/ContentElementResolver.php: parses TYPO3 typolink
  (t3://record?identifier=tt_content&uid=N, t3://page?uid=P#N, plain numeric)
  to a normalised tt_content envelope ({id,type,colPos,sorting,appearance,
  data}), recursively resolving any nested VITEC list-plugin children.
- ProductListJsonRenderer / ProductShowJsonRenderer: contentelement and
  contentelementcta now emit the resolved object instead of the raw
  typolink string (breaking change at those two keys).
- Product model: new field videofile (FAL, single video upload in tab
  Images and Videos, mp4/webm/ogv/mov/m4v); new bool field showdatapath
  (toggle at end of General tab, controls the "Datapath is now Vitec"
  graphic in the frontend). ext_tables.sql, TCA, model property +
  getter/setter, and both renderers updated accordingly.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-05 10:34:49 +02:00

72 lines
2.4 KiB
XML

<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<xliff version="1.0">
<file source-language="en" datatype="plaintext" original="EXT:vitec/Resources/Private/Language/locallang_pages.xlf" product-name="vitec">
<header/>
<body>
<trans-unit id="layout.0" resname="layout.0">
<source>Default</source>
</trans-unit>
<trans-unit id="layout.1" resname="layout.1">
<source>Index Page</source>
</trans-unit>
<trans-unit id="layout.2" resname="layout.2">
<source>Markets Overview</source>
</trans-unit>
<trans-unit id="layout.3" resname="layout.3">
<source>Market Detail</source>
</trans-unit>
<trans-unit id="layout.4" resname="layout.4">
<source>Solutions Overview</source>
</trans-unit>
<trans-unit id="layout.5" resname="layout.5">
<source>Solution Detail</source>
</trans-unit>
<trans-unit id="layout.6" resname="layout.6">
<source>Use Cases Overview</source>
</trans-unit>
<trans-unit id="layout.7" resname="layout.7">
<source>Use Case Detail</source>
</trans-unit>
<trans-unit id="layout.8" resname="layout.8">
<source>Products Overview</source>
</trans-unit>
<trans-unit id="layout.9" resname="layout.9">
<source>Product Main Category</source>
</trans-unit>
<trans-unit id="layout.10" resname="layout.10">
<source>Product Detail</source>
</trans-unit>
<trans-unit id="layout.11" resname="layout.11">
<source>Support Overview</source>
</trans-unit>
<trans-unit id="layout.12" resname="layout.12">
<source>News Overview</source>
</trans-unit>
<trans-unit id="layout.13" resname="layout.13">
<source>News Detail V1</source>
</trans-unit>
<trans-unit id="layout.14" resname="layout.14">
<source>News Detail V2</source>
</trans-unit>
<trans-unit id="layout.15" resname="layout.15">
<source>News Detail V3</source>
</trans-unit>
<trans-unit id="layout.16" resname="layout.16">
<source>Content Page V1</source>
</trans-unit>
<trans-unit id="layout.17" resname="layout.17">
<source>Content Page V2</source>
</trans-unit>
<trans-unit id="layout.18" resname="layout.18">
<source>Content Page V3</source>
</trans-unit>
<trans-unit id="layout.19" resname="layout.19">
<source>Events Overview</source>
</trans-unit>
<trans-unit id="layout.20" resname="layout.20">
<source>Contact Page</source>
</trans-unit>
</body>
</file>
</xliff>