README

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

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.1 Installation

Installation using Composer

The recommended way to install the extension is using Composer.

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

Download and install the extension with the extension manager module.

2.2 Minimal setup

1. Just install the extension and you are done

3 Report issues

Please report issue directly in the issue tracker in the Github repository.

4 Administration corner

4.1 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

Please have a look into the Github repository.

4.3 Release Management

Redirect 403 uses semantic versioning, which means, that

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

4.4 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.