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: [afbeelding] 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. (C…

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

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.

Gebruikersaanmaak via API is een puinhoop!

Ondersteuning

Canapin (Coin-coin le Canapin) 14 januari 2025 om 13:07 2

For the record, some of those were discussed here:

Topic		Antwoorden	Weergaven
Create-User via REST-API, does not seem to be working Support	5	222	3 maart 2025
User creation API: ‘active’ attribute set to True but returns False in response Support rest-api	10	262	1 januari 2025
API, create user, no longer returns user_id Support	8	253	17 april 2025
New signup with old email including + doesnt work in rest API Support	13	602	8 juni 2023
Cant create active user via api, Again Support	1	504	8 april 2021

Gebruikersaanmaak via API is een puinhoop!

Gerelateerde topics