pbAuthLogin, registration and profile

/login, /register and /profile answer the moment the package is installed — no resources to create. Form markup lands as files that belong to the site from that minute on. Social login, two-factor sign-in and manager impersonation are included.

Quick start

For developers

What is it

The zero step is empty

Install the package, check one routing setting, clear the cache — /login already opens with a working form. No resources, no templates, no snippet calls to set up.

The markup is yours from minute one

Twenty form chunks and the e-mail templates are copied into core/App/elements/auth/ and belong to the site from then on. Neither install nor upgrade ever overwrites an existing file.

A new field takes two edits

Declare it in the validation rules and add a block to the chunk. If the field has a database column, no PHP at all. Anything not in the rules is dropped — extra data cannot be slipped in.

Fourteen events instead of patches

A welcome e-mail, an audit record, a call to an external service — as a class in the config, not as a plugin you must re-attach after every upgrade. A listener that throws does not break the registration.

Six social providers, no libraries

Google, Yandex, Mail.ru, GitHub, Facebook, Telegram. The whole exchange is two requests to the provider. A provider without credentials is deliberately hidden: a button that cannot work is worse than no button.

Two-factor without SMS and without bills

The code is shown by an app on the phone; the site sends nothing — no mail, no SMS, no contract with a gateway. Eight backup codes in case the phone is lost.