CoolCMS API

UserBanStateListenerRegistry
in package

FinalYes

Finds all services implementing {@see UserBanStateListener} and notifies them (pattern of `MessageThreadReadListenerRegistry`). Resolved lazily through the container: the content managers depend on `UserManager` themselves, so injecting them into it would create a dependency cycle.

Best effort: a failing listener is logged and does not fail the user save (the ban itself, sign-in and token revocation must work even when, e.g., the search index is down).

Table of Contents

Properties

$container  : Container

Methods

__construct()  : mixed
notify()  : void

Properties

Methods

On this page

Search results