-
Notifications
You must be signed in to change notification settings - Fork 128
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
The assets for elfinder.min.js are giving 404 when using a different asset_path #497
Comments
Also can confirm that |
I am affected by this bug, when will it be merged and released? |
The fix is in #509 but there is not much activity there atm. For me i just locked my composer.json to older version for temporary fix to: |
I was thinking of using https://github.com/symplify/vendor-patches |
I can merge it guys, but didn't test for back compatiblity, if someone confirms, ok, will proceed |
Fixes #497 mainUrl didn't contain asset path
I can confirm it works for me, but thats expected since i supplied the fix. When will we get a release? @enboig maybe you can confirm it works for you? |
This update appears to have broken elfinder for us (default assets path, and also still using Symfony 6.4 in case that's relevent). With version 12.5 of this bundle, the elfinder assets are loaded from I've got a feeling that the problem is that the default value of As a workaround, you can either set the |
Ah sorry @jontjs it broke for you and probably others, i'm thinking changing the default |
Describe the bug
I have my
asset_path
configured to a different folder now with the recent changes: #493 i breaks it probably was already broke before this fix. Some more context: https://github.com/helios-ag/FMElfinderBundle/pull/493/files#r1162540304To Reproduce
Have a
asset_path
defined to different folder then the default and check you get 404 when loading the assets.The text was updated successfully, but these errors were encountered: