Since #3027639: Make css/js optimized assets path configurable, released in versions 10.1 & 11.1, Drupal uses the assets:// wrapper to store and serve aggregated CSS and JS files.
This allows people with special storage needs to separate uploaded files from generated ones.
The locale module generates files for translations used in the JS scripts (cf _locale_rebuild_js()). These generated files are located in a configurable sub folder of the public:// base folder.
Use the assets:// base folder for consistency with other generated files.
| Comment | File | Size | Author |
|---|
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes, plain diff MR !15827
Comments
Comment #3
duaelfrThe fix is quite straight forward.
I don't think it's breaking BC but we might want to put this behind a feature flag just in case, aren't we?
Patch attached for composer.
Comment #4
smustgrave commentedNot sure a feature flag but maybe a CR?
Comment #5
duaelfrNot being a native English speaker makes me fear the exercise of writing a CR.
Feel free to make it better ;)
#3592731: JavaScript translation files are now stored in the assets:// path location
Comment #6
smustgrave commentedEdited the numbers but seems good to me!
Comment #7
berdirI think this and #3487600: Use the assets stream wrapper for translated javascript files are duplicates, fine to close the other one if this is RTBC, seems like the other issue had pretty much the same changes.
Comment #11
catchCommitted/pushed to main and cherry-picked to 11.x and 11.4.x, thanks!