Skip to content

Configurable registration fields #255

Description

@Himura2la

Currently the Phone and Address field are hardcoded as required:

// Validate required fields
if ($nome === '' || $cognome === '' || $email === '' || $telefono === '' || $indirizzo === '' || $password === '' || $password !== $password2) {
return $response->withHeader('Location', RouteTranslator::route('register') . '?error=missing_fields')->withStatus(302);
}

Which is very inconvenient for small communities where we can't force members to disclose their personal information. Please, make a separate database table to allow NULLS in any field.

Also NULLS should be allowed in a cognome field, since we don't want to force users use their real names. This would require schema migration:

`cognome` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL,

After it's done, the second step is to allow adding custom fields. For example, we need a Telegram username, because that's the main platform for our community, and we're going to use it in API for notifications, etc.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions