On Discourse version v3.1.0.beta5 +233, if a new user chooses the name “adman,” “adman-b”, or “adman-c” that user’s profile is badly broken. Attempting to access the user’s public profile results in some extremely low-level failure that causes a never-ending page load (Firefox) or a simple hard error “ERR” (Chrome). This does not appear to be a trapped error. I have verified that creating a user named “adman” results in the same problem at try dot discourse dot org. No other profile setup actions are necessary–for example, you don’t need to set a profile picture, or anything else–just using a name beginning in “adman” is enough to produce the error. I have also verified that choosing “ad-man” as a username does not break the user’s profile. The username “adma” also does not result in a broken profile. I’m stumped. Again, I’ve verified that this is true on both my own self-hosted Discourse, AND on try.discourse.org. I’m not sure how long the content on try.discourse.org remains before purging, but you can see this right now by trying to load the user profile there: httpx://try dot discourse dot org/u/adman/summary Or you can see the effect by trying to look at the user “adman-c” on my self-hosted instance: httpx://discourse dot practicalzfs dot com/u/adman-c Meanwhile, user “adma” on try.discourse works fine: httpx://try dot discourse dot org/u/adma/summary

Hello and welcome @jimsalterjrs :slight_smile: I can’t replicate this. :thinking: Long-shot, but I don’t suppose it could be your ad-blocker reacting to ‘ad’ in some way? Can you try in an incognito window/ad-blocker off to check?

I’ve also confirmed that the usernames “madman” and “admyn” work properly. So it looks like there’s a regex somewhere that triggers on /^adman/ – to reproduce the bug, the username must begin with the complete sequence “adman”.

Well damn. Thank you very much, that was exactly it. The default filterset on uBlock Origin appears to be what’s breaking things, although I haven’t figured out yet which rule is getting triggered.

No worries. Glad to have helped. :slight_smile:

Any account with username "adman" has a broken profile

Product Support

jimsalterjrs (Jim Salter) July 6, 2023, 8:11pm 5

And this is the rule that triggers:

I’ll let my user know that’s a very poor choice of username, given how many people are using Easylist!

Topic		Replies	Views
Error while saving user profile Bug	3	1191	December 16, 2016
User profile page is not found (404) - emails not showing Product Support	23	1905	September 21, 2019
Attempting to use the @username feature crashes the tab Product Support	2	522	May 27, 2019
This is the problem of a specific user or something else? Product Support	6	782	October 14, 2020
Problems with two users with same name/username (but upper/lowercase) Product Support	7	2170	September 9, 2020

Any account with username "adman" has a broken profile

Related topics