PHPackages erhaweb/l10ntable-extended - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Localization & i18n](/categories/localization) 4. / 5. erhaweb/l10ntable-extended ActiveTypo3-cms-extension[Localization & i18n](/categories/localization) erhaweb/l10ntable-extended ========================== With the assistance of this extension, the localization overview within the Info module gains an enhanced "Edit all language overlay records" button, featuring individually customizable fields. This empowers users to conveniently perform batch edits on configurable page fields on page translations. 1.0.3(1y ago)0511↓40%[1 PRs](https://github.com/ErHaWeb/l10ntable_extended/pulls)GPL-2.0-or-laterPHPPHP ^8.1 || ^8.2 || ^8.3 Since Sep 7Pushed 8mo ago1 watchersCompare [ Source](https://github.com/ErHaWeb/l10ntable_extended)[ Packagist](https://packagist.org/packages/erhaweb/l10ntable-extended)[ Docs](https://extensions.typo3.org/extension/l10ntable_extended)[ RSS](/packages/erhaweb-l10ntable-extended/feed)WikiDiscussions main Synced today READMEChangelogDependencies (3)Versions (12)Used By (0) Extended Localization Table =========================== [](#extended-localization-table) TYPO3 Extension by Eric Harrer Description ----------- [](#description) With the assistance of this extension, the **Localization Overview** within the **Info** module gains an enhanced `Edit all language overlay records` button, featuring individually customizable fields. [![Edit all language overlay records button](Documentation/Images/LocalizationOverview.png)](Documentation/Images/LocalizationOverview.png) This empowers users to conveniently perform batch edits on configurable page fields on page translations. By default, only the `title`, `nav_title` and `hidden` fields are available for batch processing in the translation view. This can now be extended to any (existing) page fields. [![Batch edit pages example with configured fields](Documentation/Images/NewFieldsExample.png)](Documentation/Images/NewFieldsExample.png) Installation ------------ [](#installation) Install the extension via Composer using ``` composer req erhaweb/l10ntable-extended ``` How to use ---------- [](#how-to-use) ### Global configuration via user TSconfig [](#global-configuration-via-user-tsconfig) After the installation the following can be defined in the `User TSconfig` to define as administrator for backend user groups or single backend users which columns they can edit: ``` tx_l10ntableextended { replaceColumnsList := addToList(seo_title,description) } ``` [![User TSconfig](Documentation/Images/UserTsConfig.png)](Documentation/Images/UserTsConfig.png) In this example, the two fields `seo_title` and `description` would be added to the default fields `title`, `nav_title` and `hidden`. Of course, it is also possible to omit all or some of the fields that are used by default and use only your own fields. In this case overwrite the default list via a simple `=` statement. ``` tx_l10ntableextended { replaceColumnsList = seo_title,description } ``` Fields that are not available in the context of a page type (for example, the `seo_title` field for pages of type `Folder [254]`) are simply not displayed in the context of batch editing. Fields that do not exist in `$GLOBALS['TCA']['pages']['columns']` are **not considered at all**. ### Override global configuration in your sitepackage [](#override-global-configuration-in-your-sitepackage) Please note that your sitepackage must be loaded after the `EXT:l10ntable_extended` so that the default user TSconfig can be overwritten at file level. This can be achieved by adding the following configuration in file `ext_emconf.php` of your sitepackage extension: ``` $EM_CONF[$_EXTKEY]['constraints']['depends']['l10ntable_extended'] = ''; ``` ### Extension Configuration [](#extension-configuration) Under Admin Tools > Settings > Extension Configuration you can determine whether non-admin backend users can also determine the list of editable fields within their User Settings. Set the option for this: ``` enableUserSettings = 1 ``` [![Extension Configuration](Documentation/Images/ExtensionConfiguration.png)](Documentation/Images/ExtensionConfiguration.png) ### Configuration via the backend user settings [](#configuration-via-the-backend-user-settings) If the User Settings have been activated in the Extension Configuration, all backend users (also non-admin users) can determine the page fields that should be editable via a multiple selection field. [![Backend User Settings](Documentation/Images/BackendUserSettings.png)](Documentation/Images/BackendUserSettings.png) Tipp ---- [](#tipp) The name of the `columnsOnly` parameter, that is evaluated by the `EditDocumentController`, can be customized using the following setting. ``` tx_l10ntableextended { columnsUrlParameter = columnsOnly } ``` However, this should only be necessary if the core decides to use a different parameter to specify the columns to be edited. ### Health Score 37 — LowBetter than 81% of packages Maintenance48 Moderate activity, may be stable Popularity15 Limited adoption so far Community7 Small or concentrated contributor base Maturity65 Established project with proven stability Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~45 days Recently: every ~56 days Total 10 Last Release 620d ago Major Versions 0.3.1 → 1.0.02024-03-12 PHP version history (2 changes)0.3.1PHP ^7.4 || ^8.1 || ^8.2 || ^8.3 1.0.0PHP ^8.1 || ^8.2 || ^8.3 ### Community Maintainers ![](https://avatars.githubusercontent.com/u/5416710?v=4)[Eric Harrer](/maintainers/ErHaWeb)[@ErHaWeb](https://github.com/ErHaWeb) --- Top Contributors [![ErHaWeb](https://avatars.githubusercontent.com/u/5416710?v=4)](https://github.com/ErHaWeb "ErHaWeb (38 commits)") --- Tags localizationextensionmoduletypo3infol10ntable ### Embed Badge ![Health badge](/badges/erhaweb-l10ntable-extended/health.svg) ``` [![Health](https://phpackages.com/badges/erhaweb-l10ntable-extended/health.svg)](https://phpackages.com/packages/erhaweb-l10ntable-extended) ``` ### Alternatives [web-vision/wv_deepltranslate DeepL Translate (CORE) - This extension provides option to translate content element, and TCA record texts to DeepL supported languages. 33304.3k](/packages/web-vision-wv-deepltranslate)[web-vision/deepltranslate-core DeepL Translate (CORE) - This extension provides option to translate content element, and TCA record texts to DeepL supported languages. 33142.5k8](/packages/web-vision-deepltranslate-core)[leuchtfeuer/locate Locate - The users country, preferred language and other facts will be detected. Depending on configurable rules the user can be redirected to other languages or pages. Locate also provides geo blocking for configurable pages in configurable countries. 1186.6k](/packages/leuchtfeuer-locate)[stefanfroemken/repair_translation Get rid of displaying the default file in translated records 2364.6k](/packages/stefanfroemken-repair-translation) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)