Display full name not username when attributing quote in RTE

AI-generated summary

A discussion was opened regarding a bug where quote blocks in the Rich Text Editor (RTE) display usernames instead of full names, despite site settings configured to show full names. Jesse_Starks reported the issue, confirming that settings like prioritize_username_in_ux and display_name_on_posts were correctly enabled. Moin initially suggested the issue might stem from legacy posts lacking name data or specific user configurations, but Jesse_Starks clarified that the problem persisted even with newly created posts.

After ruling out profile name suppression issues, Moin hypothesized the bug was specific to the RTE. Through testing, Moin identified that quoting works correctly in Markdown mode but fails in WYSIWYG mode. Jesse_Starks confirmed this finding. The consensus is that the feature itself is functional, but the new RTE does not yet support displaying full names in quotes. Moin expressed gratitude for the collaboration in root-causing the issue, and zogstrip noted that a fix has been submitted to the Discourse repository via pull request #38078.

I saw an old bug topic below - where it looks like the dev team’s intention to fix this - but it seems to still be happening as of today: (quote blocks not respecting the full name setting)

Could not add a reply to this old topic - so opened a new one.

It works fine for me. “My Name” is the name, “Moin” is the username, and the quote shows the name:

How did you configure these two site settings?

Confirmed those settings. Screenshots below - first 2 are settings, last one shows the username (Meekness) in the quote rather than name (Aaron).

Is the name included in the raw post?


If you edit that post and look at it in markdown mode (toggle button at the top left), do you see both - name and username? I don’t think that information is included on posts that were created before the settings were configured like this.

The settings were configured like this a couple days ago. This topic and thread were all created today.

Here is the raw post (no name, just username)

Is the Enable names setting enabled too?

It might be something with this specific user. For some reason the UX shows his username next to his full name, but not for me.

Similarly - if I quote myself - I see the full name, not username.

Checking on that now…

Yes - enable names is set to true.

I guess your name and username are kind of the same?

There is Remove Name Suppression on Posts which was the result of this topic Allow site operators to control full name suppression on posts (but I think you were on a plan without components)

I haven’t tried if the component also helps for quotes.

2 Likes

OK, MY username and full name are the same - that is why it is being suppressed. So we can leave that aside. That returns us to the original issue. When I quote Aaron, it attributes to his username (meekness) for some reason…

I think I narrowed it down :tada:

Would you mind trying the following?

  1. Click reply on his post again
  2. Ensure the composer is in Markdown-mode
  3. Try to quote again

I think this is a bug with the rich-text-editor


Steps to reproduce the bug:

  1. Disable prioritize_username_in_ux
  2. Enable display_name_on_posts
  3. Add a name to your profile
  4. Create a post with some text and publish it
  5. Click reply on that post
  6. Ensure your composer is in Markdown mode
  7. Quote a part of the post you created and publish the reply
    → The full name is included in the quote as expected
  8. Switch to WYSIWYG mode
  9. Quote again and publish the reply
    → The full name is not included
4 Likes

You figured it out! Markdown mode shows his name

3 Likes

Thank you for your patience and for helping me track this down.

So the feature itself still works - it’s just not supported yet in the (relatively new) rich text editor. Now that we’ve identified the cause, hopefully, it’ll be fixed soon.

1 Like

Good deal - thank you! I have to say I am really loving this product - and this support forum is excellent.

2 Likes

Great work @Moin root causing this one :clap:

It made it 100x times easier to fix :+1:

https://github.com/discourse/discourse/pull/38078

6 Likes