PHPackages                             bugfix/patchlayout - 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. [Utility & Helpers](/categories/utility)
4. /
5. bugfix/patchlayout

ActiveTypo3-cms-extension[Utility & Helpers](/categories/utility)

bugfix/patchlayout
==================

Patch for Backend Layout

v0.4.0(1mo ago)0771[1 issues](https://github.com/franzholz/patchlayout/issues)1GPL-2.0-or-laterPHP

Since Sep 27Pushed 1mo ago1 watchersCompare

[ Source](https://github.com/franzholz/patchlayout)[ Packagist](https://packagist.org/packages/bugfix/patchlayout)[ Docs](https://jambage.com)[ RSS](/packages/bugfix-patchlayout/feed)WikiDiscussions master Synced yesterday

READMEChangelog (10)Dependencies (2)Versions (13)Used By (1)

TYPO3 extension patchlayout
===========================

[](#typo3-extension-patchlayout)

What is does
------------

[](#what-is-does)

This extension shall fix the TYPO3 backend error message for a frontend plugin:

**colPos: VALUE IS NOT ALLOWED (“1”)**

**colPos: WERT IST NICHT ERLAUBT (“1”)**

It seems even to work if the extension gridelements is activated.

The patch for the TYPO3 Backend Layout is inside of this extension.

TYPO3 allows to add new item values of the colPos field in the table tt\_content. Any another extension can add its own column values to the selectable columns of the content element. Only be this means it can be avoided that this content element is shown in the front end by means of TYPO3. A special column value can be used by a third party extension to do its own content rendering for it.

Maybe there is another way to avoid that TYPO3 renders a content element. It would be fine if you would tell me how. However this is a proven way which has been working until TYPO3 6.2 by simply adding this TCA override.

### example:

[](#example)

```
// Add the new colPos to the array, only if the ID does not exist...
$colPosOMyExtension = 1212;
$GLOBALS['TCA']['tt_content']['columns']['colPos']['config']['items'][$colPosOMyExtension] = [
        'LLL:EXT:myextension/locallang_db.xml:tt_content.colPosOfMyExtension',
        $colPosOMyExtension
];
```

This will add the corresponding text for the column 1212 of extension ‘myextension’ to the column select box of the TYPO3 content element.

```
'type' => 'select',
'renderType' => 'selectSingle',
```

alternative solution since TYPO3 9:
-----------------------------------

[](#alternative-solution-since-typo3-9)

pointed out by Hendrik Reimers

A hook exists in order not to show the content inside of a general backend layout column and thus to avoid any error hints about invalid columns in the TYPO3 backend. This makes it possible to define your own column in the TCA for tt\_content.

[Feature #82213](https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/9.0/Feature-82213-NewHookToDetermineIfContentRecordIsUsedUnused.html)

pointed out by Sebastian Klein

```
[request && traverse(request.getQueryParams(),'defVals/tt_content/colPos') == 202]
  TCAdefaults.tt_content {
      vd_layout = aside-box
  }
[end]
```

Keep in mind that this condition will only work when creating new content elements. Only then the query string in the backend contains the colPos. Therefore, the condition can be used for adjusting TCAdefaults, but not for TCEFORM settings.

###  Health Score

45

—

FairBetter than 91% of packages

Maintenance90

Actively maintained with recent releases

Popularity15

Limited adoption so far

Community11

Small or concentrated contributor base

Maturity56

Maturing project, gaining track record

 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 ~246 days

Recently: every ~264 days

Total

11

Last Release

49d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/4c36ec751f4996bdd88bcfca2669db1d0762e765cb449b33d47aed99ef1e1b1c?d=identicon)[franzholz](/maintainers/franzholz)

---

Top Contributors

[![franzholz](https://avatars.githubusercontent.com/u/4855265?v=4)](https://github.com/franzholz "franzholz (26 commits)")

---

Tags

layoutbackendTYPO3 CMS

### Embed Badge

![Health badge](/badges/bugfix-patchlayout/health.svg)

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

###  Alternatives

[friendsoftypo3/content-blocks

TYPO3 CMS Content Blocks - Content Types API | Define reusable components via YAML

103574.3k67](/packages/friendsoftypo3-content-blocks)[yoast-seo-for-typo3/yoast_seo

Yoast SEO for TYPO3

571.8M9](/packages/yoast-seo-for-typo3-yoast-seo)[ichhabrecht/content-defender

Define allowed or denied content element types in your backend layouts

923.2M27](/packages/ichhabrecht-content-defender)[derhansen/sf_event_mgt

Event management and registration - Configurable event management and registration extension based on ExtBase and Fluid

67347.1k11](/packages/derhansen-sf-event-mgt)[wazum/sluggi

TYPO3 extension for URL slug management with inline editing, auto-sync, locking, access control, and redirects

40543.5k](/packages/wazum-sluggi)[brotkrueml/schema

Embedding schema.org vocabulary - API and view helpers for schema.org markup

35678.3k19](/packages/brotkrueml-schema)

PHPackages © 2026

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