Hi all, I’m using Python to create users via the Discourse API. The user creation request is returning a success response, but I’m encountering an issue where the active attribute in the response is always false, even though I explicitly set it to true in the payload. The confirmed attribute is set…

[صورة] Luka: like the plus sign How is the normalize_emails site setting configured at your instance?

You can try running this script once; it might help you. Here you go: A script to create dummy users for your Discourse forum . Additionally, your script seems to work quite well, but the issue lies with the data you’re using in your CSV file. I tested your code using the following sample data: Us…

[A terminal window displaying two successful POST requests to a user registration endpoint. (Captioned by AI)] Hi @MihirR Thank you so much for your reply and for helping me out with this! I really appreciate it. I think I’ve found the problem. The issue was with the email addresses I was using …

[صورة] Luka: it reports a successful creation and activation It looks like it actually reports that the activation didn’t work, assuming that’s what "active": false means.

[صورة] Firepup Sixfifty: It looks like it actually reports that the activation didn’t work [صورة] Luka: "message": "Va\u0161 ra\u010dun je aktiviran i spreman za kori\u0161tenje." The message key in the response says “Your account is activated and ready for use.”, which is wrong.

Exactly, that’s the wrong part in the whole thing. The param says active:false while the message says “Account has been activated and ready for use”

Hi, The response param says active:false while the message says “Account has been activated and ready for use”

[صورة] Moin: normalize_emails I haven’t checked, but I will. It seems that was announced here: Enabling e-mail normalization by default

[A screenshot of a website settings page with a red box highlighting the "normalize emails" setting. (Captioned by AI)] Yes, it seems that the reason for the failure was the flag normalize_email:true it’s true by default. As I turned it off the users got created… However, the API is not considerin…

[صورة] Luka: Should I report this in discourse github ? Or open a Contribute > Bug rest-api topic :slight_smile:

API إنشاء المستخدم: تعيين سمة ‘active’ إلى True ولكن يُرجع False في الاستجابة

دعم المنتج

luigi7up (Luka) 1 يناير 2025، 10:14ص 9

لم أتحقق بعد، لكنني سأفعل. يبدو أنه تم الإعلان عن ذلك هنا: Enabling e-mail normalization by default

الموضوع		الردود	مرات العرض
Create-User via REST-API, does not seem to be working Product Support	5	316	3 مارس 2025
Can't add user via API Development rest-api	6	1515	17 نوفمبر 2020
Cant create active user via api, Again Product Support	1	549	8 أبريل 2021
Disable account confirm emails when creating users via API Development rest-api	26	7136	5 أغسطس 2020
Creating user via API Development rest-api	10	7598	5 أغسطس 2020

API إنشاء المستخدم: تعيين سمة ‘active’ إلى True ولكن يُرجع False في الاستجابة

الموضوعات ذات الصلة