Radiant RC2 - Assets - Uploading a Video Error

31 views
Skip to first unread message

James Martens

unread,
Sep 13, 2011, 1:22:48 PM9/13/11
to Radiant CMS
Hi again radiant peeps.

Another issue has cropped up for me on RC2.
In assets, I am trying to upload a video, but I am getting a very
strange error (occurs in both development and production). The error
happens as soon as I click the create asset button and appears to be
in the post process phase:


MissingSourceFile (no such file to load -- /Users/jaemo/projects/
family_justice/lib/paperclip_processors/frame_grab.rb):
paperclip (2.3.16) lib/paperclip.rb:114:in `load_processor'
paperclip (2.3.16) lib/paperclip.rb:104:in `processor'
paperclip (2.3.16) lib/paperclip/attachment.rb:359:in
`post_process_styles'
paperclip (2.3.16) lib/paperclip/attachment.rb:358:in `each'
paperclip (2.3.16) lib/paperclip/attachment.rb:358:in `inject'
paperclip (2.3.16) lib/paperclip/attachment.rb:358:in
`post_process_styles'
paperclip (2.3.16) lib/paperclip/attachment.rb:354:in
`post_process_styles'
paperclip (2.3.16) lib/paperclip/attachment.rb:348:in `post_process'
paperclip (2.3.16) lib/paperclip/callback_compatibility.rb:23:in
`call'
paperclip (2.3.16) lib/paperclip/callback_compatibility.rb:23:in
`run_paperclip_callbacks'
paperclip (2.3.16) lib/paperclip/attachment.rb:347:in `post_process'
paperclip (2.3.16) lib/paperclip/callback_compatibility.rb:23:in
`call'
paperclip (2.3.16) lib/paperclip/callback_compatibility.rb:23:in
`run_paperclip_callbacks'
paperclip (2.3.16) lib/paperclip/attachment.rb:346:in `post_process'
paperclip (2.3.16) lib/paperclip/attachment.rb:114:in `assign'
paperclip (2.3.16) lib/paperclip.rb:279:in `asset='
/Users/jaemo/.rvm/gems/ruby-1.8.7-p174@family_justice/gems/
radiant-1.0.0.rc2/vendor/extensions/clipped/app/controllers/admin/
assets_controller.rb:28:in `create'
compass (0.10.6) lib/compass/app_integration/rails/actionpack2/
action_controller.rb:7:in `process'
haml (3.0.25) rails/./lib/sass/plugin/rack.rb:41:in `call'
/Users/jaemo/.rvm/rubies/ruby-1.8.7-p174/lib/ruby/1.8/webrick/
httpserver.rb:104:in `service'
/Users/jaemo/.rvm/rubies/ruby-1.8.7-p174/lib/ruby/1.8/webrick/
httpserver.rb:65:in `run'
/Users/jaemo/.rvm/rubies/ruby-1.8.7-p174/lib/ruby/1.8/webrick/
server.rb:173:in `start_thread'
/Users/jaemo/.rvm/rubies/ruby-1.8.7-p174/lib/ruby/1.8/webrick/
server.rb:162:in `start'
/Users/jaemo/.rvm/rubies/ruby-1.8.7-p174/lib/ruby/1.8/webrick/
server.rb:162:in `start_thread'
/Users/jaemo/.rvm/rubies/ruby-1.8.7-p174/lib/ruby/1.8/webrick/
server.rb:95:in `start'
/Users/jaemo/.rvm/rubies/ruby-1.8.7-p174/lib/ruby/1.8/webrick/
server.rb:92:in `each'
/Users/jaemo/.rvm/rubies/ruby-1.8.7-p174/lib/ruby/1.8/webrick/
server.rb:92:in `start'
/Users/jaemo/.rvm/rubies/ruby-1.8.7-p174/lib/ruby/1.8/webrick/
server.rb:23:in `start'
/Users/jaemo/.rvm/rubies/ruby-1.8.7-p174/lib/ruby/1.8/webrick/
server.rb:82:in `start'


I assume frame_grab.rb is meant to take a thumbnail screencap of the
video. I cannot find any reference to this file anywhere on the
googles, so hoping someone here has some info or insight....

Happy Tuesday!
-James

James Martens

unread,
Sep 13, 2011, 1:25:03 PM9/13/11
to Radiant CMS
Also worth noting: the folder /lib/paperclip_processors/ is NON-
EXISTANT on my system. Not sure if that was supposed to get set up
during install or what...

James Martens

unread,
Sep 13, 2011, 1:31:32 PM9/13/11
to Radiant CMS
Another note: if I create a new blank RC2 radiant app, do NOTHING
other than get it running with no extensions installed, I still get
the same error message, so it seems that something is not being
installed or configured properly during the install process...

On Sep 13, 11:22 am, James Martens <j...@jjonah.com> wrote:

James Martens

unread,
Sep 14, 2011, 12:11:40 PM9/14/11
to Radiant CMS
So... No one has tried to upload a video asset?
I cannot believe I am the only one who has come across this issue, and
it has recurred on multiple machines. The absence of this file seems
to me to be a glaring oversight.

Anyone having any insight whatsoever, I am begging for your help!
Thanks!

James Martens

unread,
Sep 14, 2011, 12:42:34 PM9/14/11
to Radiant CMS
FYI for anyone else who runs into this oddball of an error, I fixed it
by copying the frame_grab.rb file from the /usr/lib/ruby/gems/1.8/gems/
radiant-1.0.0.rc2/vendor/extensions/clipped/lib/paperclip/ dir to the /
lib directory in my project.

I am skeptical that it's a path or permission error that caused the
original issue, as I posted earlier, it occurred on multiple hardware
instances.
Regardless, this appears to have resolved the issue for me, but if
anyone has better insight as to the cause, I'd love to hear your
thoughts.

Happy coding!
-James

William Ross

unread,
Sep 14, 2011, 1:11:14 PM9/14/11
to radia...@googlegroups.com
On 13 Sep 2011, at 18:22, James Martens wrote:

> Hi again radiant peeps.
>
> Another issue has cropped up for me on RC2.
> In assets, I am trying to upload a video, but I am getting a very
> strange error (occurs in both development and production). The error
> happens as soon as I click the create asset button and appears to be
> in the post process phase:
>
>
> MissingSourceFile (no such file to load -- /Users/jaemo/projects/
> family_justice/lib/paperclip_processors/frame_grab.rb):

That is an odd error, but I'm not surprised: RC2 is very old now. RC3 is about to be released and will bring in a much more recent version of the clipped extension. I would advise that you try edge radiant (from the github repository) or wait a day or so for RC3.

And yes, people have tried uploading videos. You need ffmpeg installed to get most of the benefit but it works very well.

Will


James Martens

unread,
Sep 14, 2011, 2:11:28 PM9/14/11
to Radiant CMS
Yes, you do need ffmpeg installed - RC2 will simply not boot without
it, in my (admittedly limited) experience with RC2, so this
requirement has been met already in my dev and production servers.

The issue I can see is that radiant was looking for a ruby file in the
local project directory when it should have been looking in the gem
directory (which is where I found it). The fact that this occurred on
3 systems (2 OSX/Lion, one Ubuntu 10.4) suggests to me that something
is quirky in the install process, but it's entirely possible that I
screwed up 3 separate times too :)

As you say though, this is an older build and is about to be replaced
- a very valid point.

Any ideas if upgrading to RC3 will cause significant issues from RC2?
I don't really have the luxury of time to debug tons of issues (as I
have already ported this app from 0.9 and used up a lot of my budget
in that exercise).
If it is a clean upgrade path and has significant performance benefits
over RC2 it will be worth it, otherwise it will be a difficult
decision to make, even if I do enjoy running the latest and greatest
(and as annoying as bugs are, solving problems is fun too!)

Thanks for your reply, your advice was welcome!

William Ross

unread,
Sep 14, 2011, 3:44:36 PM9/14/11
to radia...@googlegroups.com

On 14 Sep 2011, at 19:11, James Martens wrote:

> Yes, you do need ffmpeg installed - RC2 will simply not boot without
> it, in my (admittedly limited) experience with RC2, so this
> requirement has been met already in my dev and production servers.
>
> The issue I can see is that radiant was looking for a ruby file in the
> local project directory when it should have been looking in the gem
> directory (which is where I found it). The fact that this occurred on
> 3 systems (2 OSX/Lion, one Ubuntu 10.4) suggests to me that something
> is quirky in the install process, but it's entirely possible that I
> screwed up 3 separate times too :)
>
> As you say though, this is an older build and is about to be replaced
> - a very valid point.
>
> Any ideas if upgrading to RC3 will cause significant issues from RC2?
> I don't really have the luxury of time to debug tons of issues (as I
> have already ported this app from 0.9 and used up a lot of my budget
> in that exercise).
> If it is a clean upgrade path and has significant performance benefits
> over RC2 it will be worth it, otherwise it will be a difficult
> decision to make, even if I do enjoy running the latest and greatest
> (and as annoying as bugs are, solving problems is fun too!)

RC3 is architecturally much more up to date than RC2, makes proper use of Bundler and prefers to handle everything as gem dependencies. There is nothing vendored and while we've taken a lot of care to be backward compatible with older installations, the new model is much cleaner and easier to manage.

There is some unavoidable manual work in changing config.gem lines in environment.rb to gem lines in the Gemfile but otherwise you should find that it is a drop-in replacement for RC2, and a lot of what was new in that release is now quite mature, especially the asset manager.

It does depend how much customising you've done, though. There are migrations and updates that might be complicated by local changes. I would say it was definitely worth giving it a go, and that it will probably just work. But I always think that. Please let me know when it doesn't.

best,

will

James Martens

unread,
Sep 14, 2011, 5:49:48 PM9/14/11
to Radiant CMS
You make a very compelling case for upgrading Will. The absence of
vendored gems/inclusion of bundler is a huge asset to me. I will have
to assess when it's released, maybe try an upgrade on a separate
github branch for my project.

We have made *extensive* mods to the member extension however (enabled
self-activation, and the project requires members to complete "steps"
to finish an video e-learning course, so I have added a steps model to
the inner workings of it).

Only one way to find out if it works I guess... Once RC3 is out I will
take some time to see if an upgrade works. If not, there is always the
next project! I like radiant well enough to stick with it,
particularly since there seems to be increasing momentum behind it
these days.

Thanks again!
-James
Reply all
Reply to author
Forward
0 new messages