Welcome header text %{site_name} gives error: The following interpolation key is invalid: site_name

Support
1

image
image975Ă—292 18.2 KB

The following interpolation key is invalid: site_name

2

I think “Site_text” is not available. When I try to edit the text at /admin/customize/site_texts/js.welcome_banner.header.new_members?locale=en I can see that only the name is available.

Screenshot_20260103_100041_Firefox
Screenshot_20260103_100041_Firefox668Ă—447 58.8 KB

I think site_name is only available for anonymous users. I guess the description needs an update.

3

Alright thanks for the info, for now I am using CSS to put the site name. Was just having a problem underlining it in the welcome text.

4

For some reason only %site_name works for annoymous visitors.

I would like to do:

Welcome, %{preferred_display_name}, to %{site_name}!

But its not possible to do this, its making underlining/CSS adjustments difficult in this area.

image
image787Ă—276 6.75 KB

image
image896Ă—493 20.4 KB

5

That makes sense. They didn’t log in, so we don’t know who they are. There is no name for them in the database.
It’s like when someone you don’t know rings your doorbell; you won’t be able to greet them by name until they introduce themselves.

6

Yes, but I would like to use that %site_name for logged in users as well :smiley:

7

Thanks for reporting it! Looks like I over-promised which variables were available…I’ve got an update coming that will correct this.

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

8

So we still can’t add %{site_name} if user is logged in?

9

Hmm… it certainly looks that way:

532080265-bc3c6556-8b24-47a7-812f-b5050f5f81d6
532080265-bc3c6556-8b24-47a7-812f-b5050f5f81d6960Ă—922 36.7 KB

I suppose you might be able to display the site name with a Theme Component by making a request to /about.json and getting the site title (I looked at the site service and couldn’t find anything about the site title).

11

The siteSetting service might work to get the value of the title site setting

15

I looked into this, the blocker here is not accessing the value of title. It’s that the backend validates translations by extracting valid interpolation keys from the default locale strings.

So when %{site_name} is not in the default string, it is rejected as an “invalid interpolation key”.

16

I don’t know what @NateDhaliwal’s idea is. I only wanted to point out an alternative to an additional request to /about.json.

I think a custom component that copies the welcome banner but provides the site_name key for all texts would be the way to go.
Or a PR that adds site_name as available key to the texts for logged in users in core

  get headerText() {
    if (!this.currentUser) {
      return i18n("welcome_banner.header.anonymous_members", {
        site_name: this.siteSettings.title,
      });
    }

    const isNewUser = !this.currentUser.previous_visit_at;
    const key = isNewUser
      ? "welcome_banner.header.new_members"
      : "welcome_banner.header.logged_in_members";

    return i18n(key, {
      preferred_display_name: sanitize(
        prioritizeNameFallback(this.currentUser.name, this.currentUser.username)
      ),
+     site_name: this.siteSettings.title,
    });
  }
19

@hipp0 thanks again for raising this! We pushed an update that makes the site_name variable available on all three header fields:

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