Klicken auf Home vom Admin-Panel führt zu einem Fehler

Arkshine · 19. November 2023 um 22:16

Ja, ich kann das auch bestätigen.

Eingeführt hier:

github.com/discourse/discourse

DEV: Update homepage URL handling

main ← homepage-url-handling

opened 08:13PM - 14 Nov 23 UTC

davidtaylorhq

+153 -51

We want / to display one of our discovery routes/controllers, but we don't want …to register it as `discovery.index` because that would break themes/plugins which check the route name. Previously, this was handled using a variety of approaches throughout the codebase (in discourse-location, discourse-url and mapping-router). But even then, it didn't work consistently. For example, if you used an Ember method like `router.transitionTo("/")`, an empty `discovery.index` page would be rendered. This commit switches up the approach. `discovery.index` is now defined as a real route, and redirects to the desired homepage. To preserve the `/` as a 'vanity url', we patch the method on the router responsible for persisting URLs to the Ember Router and the browser. The patch identifies a relevant transition by looking for a magic query parameter. In an ideal world, we wouldn't be patching the router at all. But at least with this commit, the workaround is all in one place, and works consistently for all navigation methods.

Und der Fehler tritt hier auf:

github.com/discourse/discourse

app/assets/javascripts/discourse/app/routes/discovery-index.js

5ad3e26cf


      
          import { homepageDestination } from "discourse/lib/homepage-router-overrides";
          import { disableImplicitInjections } from "discourse/lib/implicit-injections";
          import DiscourseRoute from "./discourse";
          
          @disableImplicitInjections
          export default class DiscoveryIndex extends DiscourseRoute {
            @service router;
          
            beforeModel(transition) {
              const url = transition.intent.url;
              const params = url.split("?", 2)[1];
              let destination = homepageDestination();
              if (params) {
                destination += `&${params}`;
              }
              this.router.transitionTo(destination);
            }
          }

Sieht aus, als ob das `url`-Feld fehlt

Und es scheint nur dann aufzutreten, wenn urlMethod replaceURL ist.

Thema		Antworten	Aufrufe
Error: Something went wrong - "Error while processing route: discovery.categories" Product Support	16	1716	5. Oktober 2021
Clicking on site logo from site settings leads to error page Bug	4	372	28. November 2023
Homepage is broken for admin users Product Support	2	151	9. Juli 2024
Discourse broken after moving servers Self-hosting	15	861	10. Mai 2024
Admin Plugin page is blank - Error: There is no route named adminPlugins.index Bug	23	3827	2. Dezember 2016

Klicken auf Home vom Admin-Panel führt zu einem Fehler

Verwandte Themen