For some reason I can not delete the default “Reserved Usernames” (I could a few weeks ago, but not anymore) - they all are disabled. [image] I am logged in with admin account (the one I created during first signup after installation). There is one more admin account and for both it shows the same way The discourse is up to date I tried to login in incognito (for prevent possible cache/cookie related issues), same thing Note sure if this is related - but at some point in time I when I created a second admin account, from that (second) admin account I revoked the admin privileges of the first/initial admin and then granted admin again (so ATM both are admin). Both admins have admin and moderator privileges and are connected to admin and moderator groups [image] [image]

Hi @tig3, [תמונה] Tig: Note sure if this is related Your changes to your admin lineup are not related. The default reserved usernames are now hard-coded as mandatory values. config/site_settings.yml eb2992a62 de: "[äöüßÄÖÜẞ]" fi: "[åäöÅÄÖ]" ja: '[\p{Han}\p{Katakana}\p{Hiragana}]' ko: '\p{Hangul}' zh_CN: '\p{Han}' zh_TW: '\p{Han}' reserved_usernames: type: list list_type: compact default: "admin|moderator|administrator|mod|sys|system|community|info|you|name|username|user|nickname|discourse|discourseorg|discourseforum|support|all|here" mandatory_values: "admin|moderator|administrator|mod|sys|system|community|info|you|name|username|user|nickname|discourse|discourseorg|discourseforum|support|all|here" min_password_length: client: true default: 10 min: 8 max: 500 requires_confirmation: "simple" min_admin_password_length: client: true default: 15 min: 8 https://github.com/discourse/discourse/commit/56df077931e42749ea254a9df32154a8aa13bddc

Hi @southpaw thanks for the reply. But would not it be better to hardcode just one or two (assuming the problem is in null values of that field, from what I understand from the commit message). I mean suppose I want to create a user with “support” or “info” usernames for some messages in the forum (or just Admin), so should I just change the yml file and rebuild to be able to do so ? Thank you

If they can’t be deleted they shouldn’t be there any more. The tokens all have X symbols that make it look like I can be deleted. Or at least the Xs should be removed. The descriptive text could list the mandatory ones instead (or explain why some have no Xs, as the case may be).

[תמונה] Jonathan5: The tokens all have X symbols that make it look like I can be deleted. Or at least the Xs should be removed. I think the x symbols are removed from the mandatory values [תמונה] Tig: [image]

@southpaw I just did a fresh installation and tried editing the site_settings.yml and it does not work neither before nor after rebuild. So, could you please let me know if there is any way, so I can remove those values from mandatory so I can create users with those usernames.

I take it all back then. I looked using my forum, but now see that I need to upgrade! (Incidentally I wasn’t able to quote you as I wasn’t able to highlight any text – iPhone using Hub app.)

iPhones do that every now and then. And quite often, at same time, it refuses open the composer. Closing and re-open fixes it. This could need a bug report, but iPhones are a bit pain in the tender places and that issue isn’t consistent, so I never bothered.

[תמונה] Tig: @southpaw I just did a fresh installation and tried editing the site_settings.yml and it does not work neither before nor after rebuild. So, could you please let me know if there is any way, so I can remove those values from mandatory so I can create users with those usernames. @southpaw It worked after restarting, however still after the rebuild it gets back to default settings. Considering that the idea of that commit was to simply disallow empty values for the key, would not it be more reasonable to set the mandatory_values as some dummy value, so it would suffice the condition of not being empty and exclude all the important values from it ? Please let me know if such pull request could be accepted. Thanks

I removed a few here (info, support, and community) as mandatory values, the rest can stay as-is as they are much more likely to be confusing to members. https://github.com/discourse/discourse/pull/30089

@martin Thank you, however I believe all others should be deleted as well (leaving some random/dummy value as per my previous reply) [תמונה] Martin Brennan: the rest can stay as-is as they are much more likely to be confusing to members I believe for that reason those values already exist under default [image] and still no user can use them, unless Admin decides to allow their usage - deleting from that list from admin panel. And in my opinion for self-hosted setup its better to give a freedom to admin to decide. Please consider this scenario: I want to add account with name moderator, with existing setup I have to ssh to my server change site settings file (deleting the value in mandatory_values) and restart the container to be able to do it (and after rebuild this change is being reset). But, if all values (well, except one) from mandatory_values are deleted (but NOT from default), as Admin I can simply delete “moderator” value in admin panel (under reserved usernames), quickly rename some existing user’s username to moderator and again add the word moderator - to prevent future usage. So, with my suggested approach still all those usernames are disallowed by default, however admin can easly delete/add them whenever needed without being have to make changes in site settings files.

שמות משתמש שמורים כברירת מחדל לא ניתנים למחיקה

תמיכה

Moin 5 בדצמבר,‏ 2024,‏ 4:43pm 13

I think that depends on the language used. In a German forum, “you” isn’t confusing at all.

נושא		תגובות	צפיות
Reserved Usernames Feature completed	15	3491	6 בדצמבר,‏ 2023
Regarding reserved "admin" user name Product Support	1	480	14 בספטמבר,‏ 2021
Reserved usernames programmably? Product Support	4	704	14 בספטמבר,‏ 2023
Unicode usernames and group names Announcements new-feature	33	9580	25 בפברואר,‏ 2025
Ban/prevent certain names/words in a username? Product Support	6	535	1 באפריל,‏ 2024

שמות משתמש שמורים כברירת מחדל לא ניתנים למחיקה

נושאים קשורים