Recent changes to default settings have completely messed up user creation. normalize_emails setting is on by default, which means it is no longer possible to create a user with a + address (e.g. nikki+testuser@example.com ). hide_email_address_taken is on by default, which means it is no longer po…

For the record, some of those were discussed here: [immagine] User creation API: ‘active’ attribute set to True but returns False in response Support [A screenshot of a website settings page with a red box highlighting the "normalize emails" setting. (Cap…

[immagine] Nikki Locke: normalize_emails setting is on by default So change it back? [immagine] Nikki Locke: hide_email_address_taken is on by default, So change it back. [immagine] Nikki Locke: The create user API call returns success even if the specified user already exists …

Thanks, but how do I find out if someone is looking at these bugs?

The only one that is likely to be a bug is the lookup. That feature works in the front end, though, so it’s also unlikely that it’s a bug. For someone to treat anything as a big it’ll need to be documented as such.

La creazione dell'utente tramite API è un disastro!

Supporto

Canapin (Coin-coin le Canapin) 14 Gennaio 2025, 1:07pm 2

Per la cronaca, alcuni di questi sono stati discussi qui:

Argomento		Risposte	Visualizzazioni
Create-User via REST-API, does not seem to be working Support	5	235	Marzo 3, 2025
User creation API: ‘active’ attribute set to True but returns False in response Support rest-api	10	288	Gennaio 1, 2025
API, create user, no longer returns user_id Support	8	256	Aprile 17, 2025
New signup with old email including + doesnt work in rest API Support	13	616	Giugno 8, 2023
Cant create active user via api, Again Support	1	507	Aprile 8, 2021

La creazione dell'utente tramite API è un disastro!

Argomenti correlati