-
-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSS assets fail to load when using catch all or vanity url #245
Comments
As a quick follow up. It seems this is caused by cloudfront which is configured as an asset host. Looking at the CSS file that's served up by cloudfront I can see this:
So it's not respecting the |
The assets are namespaced under |
excid3
added a commit
that referenced
this issue
Feb 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My app has a user route at the end of my routes file to support vanity urls. E.g.
meaning I can resolve:
https://myapp.com/excid3
This seems to cause a problem with the madmin css files as they now get caught by my
users
route before they have a chance to resolve.I'm seeing the following errors as a result:
Is it possible to namespace the madmin assets to avoid this?
The text was updated successfully, but these errors were encountered: