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: [이미지] 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. (Captione…

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

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.

API를 통한 사용자 생성은 엉망입니다!

제품 지원

Canapin (Coin-coin le Canapin) 1월 14, 2025, 1:07오후 2

기록을 위해 말씀드리면, 그중 일부는 여기서 논의되었습니다:

글		댓글	조회수
Create-User via REST-API, does not seem to be working Product Support	5	317	3월 3, 2025
User creation API: ‘active’ attribute set to True but returns False in response Product Support rest-api	10	394	1월 1, 2025
API, create user, no longer returns user_id Product Support	8	369	4월 17, 2025
New signup with old email including + doesnt work in rest API Product Support	13	730	6월 8, 2023
Cant create active user via api, Again Product Support	1	552	4월 8, 2021

API를 통한 사용자 생성은 엉망입니다!

Related topics