Closed jtrost closed 9 years ago
After changing the asset prefix, did you clear out the asset cache (rake tmp:cache:clear
)? There really should be no practical difference in this case between using app/assets and vendor/assets, so I'm wondering if the issue you encountered was only coincidentally fixed by changing the asset paths.
Sorry for the late reply on this. I ran rake assets:clean
before opening this pull request, and the assets in my application were still having issues. I'm inclined to believe that this is an issue with my application specifically. Otherwise there would be other people here with the same issue.
Regardless, this is a solution that worked for me. Feel free to close this if you do not think it is helpful or constructive.
I saw the following errors in the Javascript console after setting config.assets.prefix:
Failed to load: http://localhost:3000/assets/tinymce/plugins/table/plugin.js tinymce.js?body=1 (line 4) Failed to load: http://localhost:3000/assets/tinymce/plugins/image/plugin.js tinymce.js?body=1 (line 4) Failed to load: http://localhost:3000/assets/tinymce/plugins/link/plugin.js tinymce.js?body=1 (line 4) Failed to load: http://localhost:3000/assets/tinymce/plugins/fullscreen/plugin.js tinymce.js?body=1 (line 4) Failed to load: http://localhost:3000/assets/tinymce/themes/modern/theme.js
Moving the assets from /vendor/assets/javascripts to /app/assets/javascripts will load assets with a prefix.