-
Notifications
You must be signed in to change notification settings - Fork 11
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
Symlinks don't install correctly when Composer falls back on the PHP zip library #28
Comments
Thanks for figuring this out! Unfortunately there is no way to enforce the installation of system packages.. |
That is annoying that such a simple limitation causes all this extra work. But indeed there's probably no way around it. |
@kwessel You think you can run a test with |
Tested it and it works well for me. |
Great! This means we now have an easy to reuse repo to add jQuery to any module. I have identifier 4 other modules: metaedit, metarefresh, statistics and oidc. |
I couldn't figure out why the Discopower module wasn't installing correctly inside my Docker image of SSP. The symlinks under modules/discopower/public/assets/components were being installed as text files containing the path where they would have pointed had they been symlinks. This obviously didn't work so great when my browser tried to load the Jquery Javascript for Discopower.
After further investigation, I tried installing unzip into my Docker image before running composer, and that fixed it. I now have symlinks instead of text files. Clearly, the PHP zip library doesn't understand symlinks.
If possible, installation of this module should require that the unzip or 7z binary be installed on the system and not just the PHP zip library.
If that's not possible, the documentation should at least include this requirement for proper installation.
Ideally, these symlinks wouldn't be necessary, and the disco.twig code that loads these components would point to the files directly instead of the symlinks inside of the module.
The text was updated successfully, but these errors were encountered: