Errors in console related to loading account preferences route directly

AI-generated summary

A user, merefield, reported an error when loading the account preferences route directly (http://localhost:4200/u/merefield/preferences/account) in their local development environment. The error was an Uncaught ReferenceError related to the queryParams declaration. This issue did not occur on Meta or on merefield’s Raspberry Pi development install.

After troubleshooting, including trying safe mode and re-pulling from the repository, david suggested that the issue might be related to one of the plugins bundled in the core. However, david later revealed that the problem was actually caused by the navigation mode being set to “dropdown” (not sidebar). A fix for this issue has been implemented by vinothkannans and merefield was able to reproduce the issue in the classic dropdown format on their Raspberry Pi.

http://localhost:4200/u/merefield/preferences/account

This is generating the following error currently:



Error occurred:

- While rendering:
  -top-level
    application
      discourse-root
        user
          user-nav
            horizontal-overflow-nav
              d-navigation-item
                link-to
<anonymous> discourse-boot.js:21
Uncaught ReferenceError: While generating link to route "userPrivateMessages": can't access lexical declaration 'queryParams' before initialization

This without any Theme Components or plugins installed on current dev build …

2 Likes

Hmm, I don’t see this issue on my local environment.

How about on Meta, does it work ok for you here? (meta is running Ember 5)

No issues on Meta … odd!

1 Like

Does using safe mode locally help? (I know you said there aren’t any custom plugins/themes, but perhaps it’s being affected by one of the plugins bundled in core)

1 Like

No /safe-mode makes no difference and FYI I’ve just re-pulled from repo

1 Like

David, I tried my Raspberry Pi (5 :rocket:) dev install and this doesn’t exhibit the same issue.

I’m going to assume my local install is corrupted for some reason, but it doesn’t make a lot of sense atm.

2 Likes

Aha, we had some other reports of this @merefield and managed to track it down. Looks like it happens when the navigation mode is “dropdown” (not sidebar)

@vinothkannans sorted a fix here: FIX: convert the route to Ember Octane to fix the dependency issue. by vinothkannans · Pull Request #25221 · discourse/discourse · GitHub

3 Likes

Aaaah. That’s awesome. Thanks.

1 Like

FYI I could in that configuration (classic dropdown format - which I :heart: btw) reproduce it on the Pi :+1: - what a weird one!

1 Like

This topic was automatically closed after 44 hours. New replies are no longer allowed.