It took me a long long time to figure out why I couldn’t get a dashboard to load, but it turns out it’s because of a URL clash bug. And not because the URLs are identical.
I have a Published Folder with the URL /Anonymisation
I created a dashboard with the URL /AnonymisationEditor
The dashboard would not load while ever its URL contained and began with the URL of a published folder.
I tried a few other combinations and I’m fairly sure this is the cause.
Agreed. This is a bug/enhancement that could use an issue.
Long story:
We kinda have a fundamental issue with URL validation across features. It’s pretty manual right now and I have actually run into this very problem recently. We implemented some checks but they’re not extensive and pretty error prone. Hence the CVE.
We do too much manual route checking and should really fall back on ASP.NET endpoint APIs to handle all this. We implemented that for apps in v5 but haven’t rolled it out across the platform. It would solve a lot of these types of issues but is a big churn.
There are issues for general URL fixes but haven’t bubbled up in a release yet.
It’s less of an issue now I worked out what’s going on. I can work around it.
But I honestly spent a long time trying to figure out why this one App wouldn’t load. There’s no clues in the logs because the admin area shows it running, the API response shows it running, there’s nothing in the App logs because for all intents and purposes, the App is running - it’s just not accessible from the front end.
