PHPackages                             kitzberger/fox-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. kitzberger/fox-handler

ActiveTypo3-cms-extension

kitzberger/fox-handler
======================

TYPO3 Fox Handler

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

Since Jun 10Pushed 3mo agoCompare

[ Source](https://github.com/kitzberger/fox_handler)[ Packagist](https://packagist.org/packages/kitzberger/fox-handler)[ Docs](https://github.com/kitzberger/fox_handler)[ RSS](/packages/kitzberger-fox-handler/feed)WikiDiscussions master Synced 1mo 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

41

—

FairBetter than 89% of packages

Maintenance53

Moderate activity, may be stable

Popularity23

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity66

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

806d 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-fox-handler/health.svg)

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

###  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)[derhansen/sf_event_mgt

Configurable event management and registration extension based on ExtBase and Fluid

64313.9k6](/packages/derhansen-sf-event-mgt)[brotkrueml/schema

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

33584.6k13](/packages/brotkrueml-schema)[in2code/in2publish_core

Content publishing extension to connect stage and production server

40135.8k](/packages/in2code-in2publish-core)[causal/image_autoresize

Simplify the way your editors may upload their images: no complex local procedure needed, let TYPO3 automatically resize down their huge images/pictures on-the-fly during upload (or using a command for batch processing) and according to your own business rules (directory/groups). This will highly reduce the footprint on your server and speed-up response time if lots of images are rendered (e.g., in a gallery). Features an EXIF/IPTC extractor to ensure metadata may be used by the FAL indexer even if not preserved upon resizing.

19455.6k](/packages/causal-image-autoresize)[causal/extractor

This extension detects and extracts metadata (EXIF / IPTC / XMP / ...) from potentially thousand different file types (such as MS Word/Powerpoint/Excel documents, PDF and images) and bring them automatically and natively to TYPO3 when uploading assets. Works with built-in PHP functions but takes advantage of Apache Tika and other external tools for enhanced metadata extraction.

16244.5k](/packages/causal-extractor)

PHPackages © 2026

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