PHPackages                             b13/pagetsconfig - 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. b13/pagetsconfig

ActiveTypo3-cms-extension

b13/pagetsconfig
================

Advanced configuration options for Page TsConfig

3.2.0(1mo ago)520.2k↓18.6%1GPL-2.0-or-laterPHP

Since Sep 23Pushed 1mo ago10 watchersCompare

[ Source](https://github.com/b13/pagetsconfig)[ Packagist](https://packagist.org/packages/b13/pagetsconfig)[ Docs](https://b13.com)[ RSS](/packages/b13-pagetsconfig/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (3)Dependencies (2)Versions (9)Used By (0)

TYPO3 Extension "Pagetsconfig"
==============================

[](#typo3-extension-pagetsconfig)

About this extension
--------------------

[](#about-this-extension)

TYPO3's out of the box configuration options to change the way editors interact with content are impressive and cover almost all use cases we encounter in our daily work. Changing backend forms for example for content element types globally or for a specific content element type is a breeze — you can just override global TCA settings. Changing some other elements, like a field label, hiding a specific field in a specific content element type within just parts of your TYPO3 instance (whether for one of your page trees or a part of a larger page tree) is easy to do using Page TsConfig.

Sometimes, though, you might want some more options than ship with TYPO3 core. At least we do from time to time. For advanced use cases we created (and use) this extension.

This extension enables advanced configuration options using Page TsConfig for special use cases.

Use cases for this extension
----------------------------

[](#use-cases-for-this-extension)

### Changing configuration for a field

[](#changing-configuration-for-a-field)

Sometimes you might need to adjust configuration for a field for parts of your TYPO3 page tree, like when working with multi-site setups. You can change the configuration for the `header` field using:

```
TCEFORM.tt_content.header.config.type = text
TCEFORM.tt_content.header.config.rows = 2

```

This also works for certain the types only:

```
TCEFORM.tt_content.header.types.my_example_type.config.type = text
TCEFORM.tt_content.header.types.my_example_type.config.rows = 3
TCEFORM.tt_content.header.types.my_example_type.config.cols = 25

```

### Changing configuration for inline fields

[](#changing-configuration-for-inline-fields)

Depending on your frontend design your "Element Component 1" might feature an image with a full palette of fields for meta data - alt text, title text, a link etc. For parts of your page tree, though, the element uses a different frontend template and some of these fields are ignored. Your editor might be confused about a "link" field, that does not do anything. Here's how to change a `showitem` configuration for an inline field:

```
TCEFORM.tt_content {
  image.types.component-1.config.overrideChildTca.types.2.showitem = --palette--;;basicImageoverlayPalette, --palette--;;filePalette
}

```

### Changing crop variants using PageTS

[](#changing-crop-variants-using-pagets)

We maintain TYPO3 instances with multiple websites using a common set of templates and content element types. We normally set fixed cropVariants for all image assets an editor can use in a specific element if the design calls for a specific aspect ratio; often times more than one, depending on the design.

Sometimes we have a set of teaser elements in such a template package, the default ratio for this element's image is 4:3, but for some reason two out of your 70 websites built upon that template package use a design slightly different and want to have a 16:9 image ratio for that specific element.

This extension enables the use of Page TsConfig to alter available cropVariant settings:

```
TCEFORM.tt_content.image.types.my_example_teaser.config.overrideChildTca.columns.crop.config.cropVariants {
  default {
    allowedAspectRatios.default.title = 16:9
    allowedAspectRatios.default.value = 1.77
    selectedRatio = default
  }
}

```

Depending on our use case we can change a setting for an existing named cropVariant, or add a new one — sometimes there's no cropVariant set globally to begin with (and we set everything using PageTS), sometimes there's the need to change on part.

This is also possible for inline records, their values and their respective settings (`tx_listelements_list` being an inline element created using EXT:listelements):

```
TCEFORM.tt_content {
  tx_listelements_list.types.timeline.config.overrideChildTca.columns.images.config.overrideChildTca.columns.crop.config.cropVariants {
    default.title = My new title
    allowedAspectRatios.1:1.title = 1:1
    allowedAspectRatios.1:1.value = 1
    selectedRatio = 1:1
  }
}

```

### Changing palette configuration

[](#changing-palette-configuration)

Sometimes it makes sense to rearrange fields in the backend within a palette for one of your page trees, for example because it helps the editor to better recognize the connection between the backend form and the frontend design. It is possible using Page TsConfig to change settings for palettes:

```
# move the "media" field from example-palette-2 to example-palette-1
TCEFORM.tt_content {
  palettes.types.startpage-header.startpage-header-media.label = Custom palette title
  palettes.types.startpage-header.startpage-header-media.showitem = image, --linebreak--, media
  # an empty palette will not be shown at all
  palettes.types.startpage-header.startpage-header-media-desktop.showitem =
}

```

Important note: While you can mess with the order of fields that way, you cannot add a field entirely. The TCA `showitem`configuration determines which fields are available for your backend form; you might need to add a field globally, remove it globally and enable it for a specific page tree depending on your use case.

When to not use this extension
------------------------------

[](#when-to-not-use-this-extension)

If you want to change some setting for some backend form globally, always put your configuration in `TCA/Overrides`!

Credits
-------

[](#credits)

This extension was created by Benni Mack way back in 2013, and repurposed 2022 by David Steeb for [b13 GmbH, Stuttgart](https://b13.com).

[Find more TYPO3 extensions we have developed](https://b13.com/useful-typo3-extensions-from-b13-to-you) that help us deliver value in client projects. As part of the way we work, we focus on testing and best practices to ensure long-term performance, reliability, and results in all our code.

###  Health Score

55

—

FairBetter than 98% of packages

Maintenance88

Actively maintained with recent releases

Popularity33

Limited adoption so far

Community16

Small or concentrated contributor base

Maturity68

Established project with proven stability

 Bus Factor1

Top contributor holds 53.6% 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 ~766 days

Recently: every ~919 days

Total

6

Last Release

59d ago

Major Versions

1.2.0 → 2.0.02023-07-26

2.0.0 → 3.0.02023-12-05

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/2851821?v=4)[b13 GmbH](/maintainers/b13)[@b13](https://github.com/b13)

---

Top Contributors

[![davidsteeb](https://avatars.githubusercontent.com/u/3862523?v=4)](https://github.com/davidsteeb "davidsteeb (15 commits)")[![achimfritz](https://avatars.githubusercontent.com/u/2152991?v=4)](https://github.com/achimfritz "achimfritz (5 commits)")[![bmack](https://avatars.githubusercontent.com/u/165630?v=4)](https://github.com/bmack "bmack (4 commits)")[![Schlumminator](https://avatars.githubusercontent.com/u/3931833?v=4)](https://github.com/Schlumminator "Schlumminator (4 commits)")

---

Tags

TYPO3 CMSPage TsConfig

### Embed Badge

![Health badge](/badges/b13-pagetsconfig/health.svg)

```
[![Health](https://phpackages.com/badges/b13-pagetsconfig/health.svg)](https://phpackages.com/packages/b13-pagetsconfig)
```

###  Alternatives

[fluidtypo3/vhs

This is a collection of ViewHelpers for performing rendering tasks that are not natively provided by TYPO3's Fluid templating engine.

1954.1M49](/packages/fluidtypo3-vhs)[bk2k/bootstrap-package

Bootstrap Package delivers a full configured frontend theme for TYPO3, based on the Bootstrap CSS Framework.

357891.4k72](/packages/bk2k-bootstrap-package)[apache-solr-for-typo3/solr

Apache Solr for TYPO3 - Apache Solr for TYPO3 is the enterprise search server you were looking for with special features such as Faceted Search or Synonym Support and incredibly fast response times of results within milliseconds.

1473.0M32](/packages/apache-solr-for-typo3-solr)[mask/mask

Create your own content elements and page templates. Easy to use, even without programming skills because of the comfortable drag and drop user interface. Stored in structured database tables. Style your frontend with Fluid tags. Ideal, if you want to switch from Templavoila.

1391.6M10](/packages/mask-mask)[ichhabrecht/content-defender

Define allowed or denied content element types in your backend layouts

892.9M22](/packages/ichhabrecht-content-defender)[lochmueller/staticfilecache

Transparent static file cache solution using mod\_rewrite and mod\_expires. Increase performance for static pages by a factor of 230!!

1311.3M3](/packages/lochmueller-staticfilecache)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)