Featured Topics

[manuel (Manuel Kostka)]

Ah right, I used a new container library from core, so right now it needs the latest Discourse version to update. Will set the correct minimum version in the component. Thanks!

[cogdog (Alan Levine)]

My site is running Discourse 2026.8.0-latest.1 but the componet displays a warning that I need to be running this version.

[Helga_Razinkova (Helga)]

Same for me, I see the same error

[manuel (Manuel Kostka)]

Thanks, I updated the compatibility version!

[Helga_Razinkova (Helga)]

Fixed! Thanks so much

[cogdog (Alan Levine)]

Our featured topics are back, thank you for the fix.

[RGJ (Richard - Communiteq)]

@manuel

Thanks, I updated the compatibility version!

It’s also broken on 2026.1 ESR at this moment

The compat file needs 2026.1.999: 0321b6d

[manuel (Manuel Kostka)]

Thanks, updated compatibility again!

This is really more involved than I expected! Looking at it, discourse/ui-kit/* imports only landed in 2026.5.0. So I set the ceiling to 2026.4.999 rather than 2026.1.999. But let me know if I’m missing something still

[RGJ (Richard - Communiteq)]

Thanks!

@manuel

to 2026.4.999 rather than 2026.1.999

Yes, that is probably better - I was lazy and I figured that version is not supported anymore anyway

[cogdog (Alan Levine)]

I saw an update for this component, and the latest version has once again broken on my site. I see again this error:

Yet my discourse is 2026.8.0-latest.1

??

[manuel (Manuel Kostka)]

Updated and set minimum version to 2026.7.999.

What apparently happens is that any suffix is treated as a pre-release, so 2026.8.0-latest.1 sorts below 2026.8.0.

I think that’s quite unintuitive and posted a bug report:

Minimum_discourse_version fails its check on -latest builds (e.g. 2026.8.0-latest.1)

Themes/components on the default latest channel get auto-disabled, and theme authors must use unintuitive workarounds. Ran into this here: Featured Topics - #76 by cogdog It’s quite unintuitive that all minimum versions need to use a format like xxx.x.999 below the current version they should actually match. Platform Self-hosted Discourse on the latest branch Discourse version: 2026.8.0-latest.1 Affects: theme/theme-component authoring (about.json metadata) and theme compatibility checks Des…

Edit: Learned on the above topic that current best practice is to not use these values at all, but use the compatibility branches. The current setup should work, but when I find time I’ll update the component to use branches.

[Orioni (John)]

Good morning, @manuel

Hope you’re doing well today.

I’ve noticed an issue where the topic author don’t show up. Custom names do, but default names don’t. The field is empty.

Code sample attached:

<div class="topic-author">
      <a aria-label="Kolhar's profile" data-user-card="Kolhar" href="/u/kolhar" tabindex="0">
  
        <img alt="" width="24" height="24" src="/user_avatar/eurth.org/kolhar/48/300_2.png" class="avatar" title="Kolhar">
        <span class="topic-author-name"></span>
      
</a>
    </div>

[manuel (Manuel Kostka)]

Hey @Orioni, how does that relate to the component? That’s the topic author code it ships:

    <div class="topic-author">
      <DUserLink @user={{@topic.creator}}>
        {{dAvatar @topic.creator imageSize="small"}}
        <span class="topic-author-name">{{@topic.creator.name}}</span>
      </DUserLink>
    </div>