-
Notifications
You must be signed in to change notification settings - Fork 66
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
Publish extension assets during installation #3273
Comments
And when an extension is upgraded? Removed when uninstalled? |
Yes. |
This needs to be done for modules as well as themes. |
the difficulty here is that the web user (php?) may not have rights to the If the rights issue is worked out, then this is pretty straightforward, I think.
|
Modules should also be able to perform custom push/copy operations. For example if images are dynamically generated they need to be copied into the |
again - I don't see how this can be done as there will be a rights/access issue to the |
possible if we depend that on #3438 ;-) |
actually, this was originally implemented
but it is commented because the feature takes too long. |
refs #3804 |
Moved to 3.0.0 because index.php will be moved into public folder! |
FYI - this is now done 'on demand' when the asset is needed and not found, it is copied from the bundle
|
Proposal for a first solution of this task: An event handler should remove all assets from |
agreed |
When an extension is installed, it's assets should be copied into the appropriate subfolder of
web
.The text was updated successfully, but these errors were encountered: