Closed akicho8 closed 11 years ago
Same problem here. Any solutions on this?
Same here.
I'm having the same issue here :S
Firstly, sorry it has taken me so long to look into this issue.
From what I can tell, the issue is caused by both tinymce-rails and turbo-sprockets making modifications to the manifest.yml
file. Since turbo-sprockets doesn't reload the manifest file after tinymce-rails make its changes, it finds files that no longer exist (that have already had their digests removed).
To fix, I see two possible strategies:
a) Quick fix turbo-sprockets to ignore files from the manifest that no longer exist.
b) Have turbo-sprockets reload the manifest file before processing the nondigest assets.
I have created a fork of turbo-sprockets-rails3 at https://github.com/spohlenz/turbo-sprockets-rails3 which contains a fix using strategy a), although b) would probably be a more robust option. It passes all of turbo-sprockets tests but I'm unsure if there are any further consequences to this approach, hence I haven't made a pull request yet.
Do you plan to make a pull request?
@spohlenz How is it solved?
@piglop Either a) use my fork above, b) upgrade to Rails 4, or c) someone else can make a pull request to turbo-sprockets-rails3. Judging from the project's lack of activity I'd suggest option a) or b).
I do not know whether there is cause to either tinymce, the turbo-sprockets-rails3. However, for the time being, I will report.
Append
gem 'turbo-sprockets-rails3'
to Gemfile