-
-
Notifications
You must be signed in to change notification settings - Fork 27
Relative Asset Paths #480
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
Comments
I got same problem: It tries to access |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
issue is still a problem, but can't really be fixed that way with how webpack is right now :( |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
the problem still exist |
Environment
Sonata packages
show
Subject
We're using symfony instances on our staging system in subdirectories. Unfortunately we ran into the problem, that the public assets of the sonataform bundle points to absolute paths.
I think the paths need an relative "./" to be more flexible. See entrypoints.json and manifest.json.
I'm not so familiar with the webpack config, but I think changing the public path may deals with this fact, see webpack.config.js.
The text was updated successfully, but these errors were encountered: