PHPackages                             ehaerer/redirect-403 - 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. [Authentication &amp; Authorization](/categories/authentication)
4. /
5. ehaerer/redirect-403

ActiveTypo3-cms-extension[Authentication &amp; Authorization](/categories/authentication)

ehaerer/redirect-403
====================

Redirect error 403 to login page or information page

3.0.0(3w ago)091GPL-2.0-or-laterPHPPHP ^8.2

Since Mar 21Pushed 3w ago1 watchersCompare

[ Source](https://github.com/Kephson/redirect_403)[ Packagist](https://packagist.org/packages/ehaerer/redirect-403)[ Docs](https://ephra.im)[ RSS](/packages/ehaerer-redirect-403/feed)WikiDiscussions main Synced 2w ago

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

TYPO3 Extension `redirect_403`
==============================

[](#typo3-extension-redirect_403)

> Basic redirect error 403 to login page or information page and bring user back to target url after login.

1 Features
----------

[](#1-features)

- Redirect user to login page if not logged in
- Redirect user to information page if logged in but no access to page
- Redirect user after login to target url

2 Usage
-------

[](#2-usage)

### 2.1 Installation

[](#21-installation)

#### Installation using Composer

[](#installation-using-composer)

The recommended way to install the extension is using [Composer](https://getcomposer.org/).

Run the following command within your Composer based TYPO3 project:

```
composer require ehaerer/redirect-403

```

#### Installation as extension from TYPO3 Extension Repository (TER) - not recommended

[](#installation-as-extension-from-typo3-extension-repository-ter---not-recommended)

Download and install the [extension](https://extensions.typo3.org/extension/redirect_403/) with the extension manager module.

### 2.2 Minimal setup

[](#22-minimal-setup)

1. Just install the extension and you are done

3 Report issues
---------------

[](#3-report-issues)

Please report issue directly in the [issue tracker in the Github repository](https://github.com/Kephson/redirect_403).

4 Administration corner
-----------------------

[](#4-administration-corner)

### 4.1 Settings in the site configuration

[](#41-settings-in-the-site-configuration)

- **protectedInfoLink** - Select a page with information why the users has no access here
- **loginPageLink** - Select a page where to find the login module

Your errorHandling configuration should look like this in your **/config/sites/my-site.yaml** file:

```
    errorHandling:
      - errorCode: 403
        errorHandler: PHP
        errorPhpClassFQCN: EHAERER\Redirect403\Error\ErrorHandler
        protectedInfoLink: 't3://page?uid=1'
        loginPageLink: 't3://page?uid=2'

```

### 4.2 Changelog

[](#42-changelog)

Please have a look into the [Github repository](https://github.com/Kephson/redirect_403).

### 4.3 Release Management

[](#43-release-management)

Redirect 403 uses [**semantic versioning**](https://semver.org/), which means, that

- **bugfix updates** (e.g. 1.0.0 =&gt; 1.0.1) just includes small bugfixes or security relevant stuff without breaking changes,
- **minor updates** (e.g. 1.0.0 =&gt; 1.1.0) includes new features and smaller tasks without breaking changes,
- and **major updates** (e.g. 1.0.0 =&gt; 2.0.0) breaking changes wich can be refactorings, features or bugfixes.

### 4.4 Contribution

[](#44-contribution)

**Pull Requests** are gladly welcome! Nevertheless please don't forget to add an issue and connect it to your pull requests. This is very helpful to understand what kind of issue the **PR** is going to solve.

Bugfixes: Please describe what kind of bug your fix solve and give us feedback how to reproduce the issue. We're going to accept only bugfixes if we can reproduce the issue.

Features: Not every feature is relevant for the bulk of `redirect_403` users. In addition: We don't want to make `redirect_403`even more complicated in usability for an edge case feature. It helps to have a discussion about a new feature before you open a pull request.

###  Health Score

45

—

FairBetter than 91% of packages

Maintenance95

Actively maintained with recent releases

Popularity10

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity58

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

Total

2

Last Release

22d ago

Major Versions

2.0.0 → 3.0.02026-07-27

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/2724872?v=4)[Ephraim Härer](/maintainers/Kephson)[@Kephson](https://github.com/Kephson)

---

Top Contributors

[![Kephson](https://avatars.githubusercontent.com/u/2724872?v=4)](https://github.com/Kephson "Kephson (13 commits)")

---

Tags

errorredirectTYPO3 CMS403

### Embed Badge

![Health badge](/badges/ehaerer-redirect-403/health.svg)

```
[![Health](https://phpackages.com/badges/ehaerer-redirect-403/health.svg)](https://phpackages.com/packages/ehaerer-redirect-403)
```

###  Alternatives

[friendsoftypo3/content-blocks

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

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

Yoast SEO for TYPO3

571.8M9](/packages/yoast-seo-for-typo3-yoast-seo)[typo3/cms-fluid-styled-content

TYPO3 CMS Fluid Styled Content - Fluid templates for TYPO3 content elements.

229.7M434](/packages/typo3-cms-fluid-styled-content)[netresearch/rte-ckeditor-image

Image support in CKEditor for the TYPO3 ecosystem - by Netresearch

631.1M8](/packages/netresearch-rte-ckeditor-image)[typo3/cms-seo

TYPO3 CMS SEO - SEO features including specific fields for SEO purposes, rendering of HTML meta tags and sitemaps.

169.1M175](/packages/typo3-cms-seo)[typo3/cms-form

TYPO3 CMS Form - Flexible TYPO3 frontend form framework that comes with a backend editor interface.

147.8M288](/packages/typo3-cms-form)

PHPackages © 2026

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