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. (Captioned by AI)] Yes, it…

[图片] 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 proble…

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) 2025 年1 月 14 日 13:07 2

就此记录，其中一些在这里已讨论过：

话题		回复	浏览量
Create-User via REST-API, does not seem to be working Support	6	180	2025 年4 月 2 日
User creation API: ‘active’ attribute set to True but returns False in response Support rest-api	11	217	2025 年1 月 31 日
API, create user, no longer returns user_id Support	8	217	2025 年4 月 17 日
New signup with old email including + doesnt work in rest API Support	14	561	2023 年7 月 8 日
Cant create active user via api, Again Support	1	500	2021 年4 月 8 日

通过API创建用户一团糟！

相关话题