PHPackages                             kitzberger/40x-handler - 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 &amp; Helpers](/categories/utility)
4. /
5. kitzberger/40x-handler

Abandoned → [kitzberger/fox-handler](/?search=kitzberger%2Ffox-handler)Typo3-cms-extension[Utility &amp; Helpers](/categories/utility)

kitzberger/40x-handler
======================

TYPO3 Fox Handler

4.0.1(2y ago)04241[1 PRs](https://github.com/kitzberger/fox_handler/pulls)GPL-2.0-or-laterPHP

Since Jun 10Pushed 5mo agoCompare

[ Source](https://github.com/kitzberger/fox_handler)[ Packagist](https://packagist.org/packages/kitzberger/40x-handler)[ Docs](https://github.com/kitzberger/fox_handler)[ RSS](/packages/kitzberger-40x-handler/feed)WikiDiscussions master Synced 2d ago

READMEChangelog (2)Dependencies (1)Versions (14)Used By (0)

TYPO3 Extension fox\_handler
============================

[](#typo3-extension-fox_handler)

This extension provides a handler for page access errors (formerly known as `pageNotFoundHandler`) that is able to handle 403 responses.

Installation
------------

[](#installation)

### Configuration

[](#configuration)

#### With site configurations (modern)

[](#with-site-configurations-modern)

In the site configuration mask you need to setup a PHP error handler pointing to `Kitzberger\FourOhExHandler\ErrorHandler` and set the 404 respective 403 page(s): [![site configuration mask](Documentation/Images/site-configuration.png)](Documentation/Images/site-configuration.png)

### 403 pages

[](#403-pages)

Here you've got two options:

- set it to a single pid, e.g. `123`
- set it to a mapping of "fe\_groups to pids", e.g. `40=3601,64=3602`

The latter example means that the user is being forwarded to

- page 3601 when accessing a page that's only visible for fe\_group 40
- page 3602 when accessing a page that's only visible for fe\_group 64

In either case the user is being forwarded with an additional GET parameter `redirect_url` containing the accessed URL.

Hint:

- Use `-2` as fe\_group option "Show at any login".
- Use `*` as a wild card. Makes sense at the end of the mapping list.

Here's an example page's "Usergroup Access Rights": [![page's Usergroup Access Rights](Documentation/Images/page-usergroup-access-rights.png)](Documentation/Images/page-usergroup-access-rights.png)

When determining the right 403 page the extension checks for all of the pages fe\_groups for which one a 403 page has been configured. The first one found will be taken.

Trouble shooting
----------------

[](#trouble-shooting)

The extension uses TYPO3's logger interface, so by adding this to your configuration (e.g. `AdditionalConfiguration.php`) you can have a look into the program's flow:

```
$logWriterConf = [
    'Kitzberger' => [
        'FourOhExHandler' => [
            'writerConfiguration' => [
                \TYPO3\CMS\Core\Log\LogLevel::DEBUG => [
                    \TYPO3\CMS\Core\Log\Writer\FileWriter::class => [
                        'logFileInfix' => 'fox-handler'
                    ],
                ],
            ],
        ],
    ],
];
$GLOBALS['TYPO3_CONF_VARS']['LOG'] = array_replace_recursive($GLOBALS['TYPO3_CONF_VARS']['LOG'], $logWriterConf);
```

###  Health Score

37

—

LowBetter than 81% of packages

Maintenance49

Moderate activity, may be stable

Popularity13

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity67

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

Recently: every ~281 days

Total

12

Last Release

849d ago

Major Versions

1.2.1 → 2.0.02021-02-02

2.0.1 → 3.0.02022-05-25

3.0.0 → 4.0.02022-11-16

### Community

Maintainers

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

---

Top Contributors

[![kitzberger](https://avatars.githubusercontent.com/u/1405149?v=4)](https://github.com/kitzberger "kitzberger (42 commits)")

---

Tags

TYPO3 CMS

### Embed Badge

![Health badge](/badges/kitzberger-40x-handler/health.svg)

```
[![Health](https://phpackages.com/badges/kitzberger-40x-handler/health.svg)](https://phpackages.com/packages/kitzberger-40x-handler)
```

###  Alternatives

[friendsoftypo3/content-blocks

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

101466.4k45](/packages/friendsoftypo3-content-blocks)[derhansen/sf_event_mgt

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

65329.4k9](/packages/derhansen-sf-event-mgt)[wazum/sluggi

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

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

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

34628.4k14](/packages/brotkrueml-schema)[yoast-seo-for-typo3/yoast_seo

Yoast SEO for TYPO3

511.7M9](/packages/yoast-seo-for-typo3-yoast-seo)[lochmueller/calendarize

Create a structure for timely controlled tables (e.g. events) and one plugin for the different output of calendar views (list, detail, month, year, day, week...). The extension is shipped with one default event table, but you can also 'calendarize' your own table/model. It is completely independent and configurable! Use your own models as event items in this calender. Development on https://github.com/lochmueller/calendarize

76161.6k13](/packages/lochmueller-calendarize)

PHPackages © 2026

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