Problem with beta6: Header Link Theme Component no longer working

AI-generated summary

After upgrading from Discourse beta5 to beta6, GuidoD reported that the Header Link Theme Component stopped displaying custom header links. Although error logs pointed to issues with the discourse-locations plugin, no direct errors were logged for the header component. davidkingham suggested disabling the locations plugin, which resolved the issue for them. Stephen confirmed this workaround and noted that the locations plugin is known to conflict with components in recent versions, citing a message from angus indicating no updates until June 1. He also reminded users to report plugin/component issues in their respective topic threads rather than in Product Support. tshenry asked whether FontAwesome 5 icon names were being used, but GuidoD confirmed they were already updated and that the issue wasn’t icon-related — links were entirely missing, not just icons. Ultimately, GuidoD confirmed that disabling the locations plugin and rebuilding the app restored the header links, validating the workaround.

I just did upgrade vom beta5 to beta6 and now the Header Link Theme Component is no longer working.
All our custom header links are no longer shown in the header.
Looks like something in the new beta has stopped the component from working.

We are now on 2.5.0.beta6 ( b3c8d36412 )

The error log does only show a lot of errors concerning the discourse-locations Plugin but nothing concerning the header problem.

The locations plugin is currently causing a lot of problems with components, try disabling it and I’m guessing your problem will go away (it did for me)

If you disable Locations (by commenting it out in the YML file and rebuilding) does the Header Link component start working again?

@davidkingham is right, Locations has a few issues with the latest tests-passed, and as mentioned here:

It’s definitely worth posting in the respective topics for any theme components and plugins, rather than here in Support, which typically deals with issues related to core. Remember that many plugins come from third parties, so the only way they’re going to find out about issues is if you participate in their topics.

Can you check to make sure you are using FontAwesome 5 icon names in your theme settings? Here’s what was recently posted in the component’s topic:

https://meta.discourse.org/t/iconified-header-links/86307/75?u=tshenry

those I had already replaced a couple of months ago (or already somewhere last year) they are up-to-date. But then there would be an empty place due to the missing button but the link itself would still be there when moving the mouse of the link location.

I know but those were plugins and theme components from the team and the theme component had been unchanged in github.
But disabling the locations plugins and rebuilding the app did work, the buttons are back.