Closed (cannot reproduce)
Project:
Video
Version:
6.x-4.2
Component:
Miscellaneous
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
7 Jun 2011 at 20:59 UTC
Updated:
18 Dec 2011 at 17:38 UTC
Please excuse me if my question comes from a fundamental misunderstanding of how things work. I'm very new to Drupal. I have Amazon S3 set up in the Video Module and after I run Cron the video files I'm uploading through a field turn up in my S3 bucket. When I go to edit the node that I uploaded the video file on though, the link visible on the edit node page points to the Drupal file system. Shouldn't it be pointing to the URL I see associated with the copy on S3? Is there a way other than this admittedly weird method for determining whether the file in the player (Flowplayer) is pointing to the S3 or the Drupal FS version? Should this duplication be occurring? I'm confused. Thanks.
Comments
Comment #1
kenwen commentedHi there,
getting the same thing I think. Checked logs and there is the following FileField was trying to display the file sites/xxxxxx/files/videos/herts_KB_course_demo_reel.mp4, but it does not exist.
Comment #2
Andrupal commentedI can confirm I'm having the same issue on my site. Watchdog is full of errors that video files do not exist.
Comment #3
kenwen commentedokay, think i found the solution
in the video enabled content type you need to set display fields for the full node to video
now to solve the mystery of the weirdly sized thumbnails...:)
Comment #4
kenwen commentedokay, video now plays but still getting multiple filefield errors in the logs
Comment #5
bcobin commentedSame issue here, even though I'm not using S3.
Once transcoded, the original video file is moved from the sites/default/files folder to sites/default/videos/original and the system keeps looking for the original file, which is no longer there. This is a bug.
There should also be the ability to delete the original video, as well as deleting files upon an unsuccessful transcode, but I'm getting ahead of myself.
Comment #6
Jorrit commentedPlease try version 6.x-4.5 or version 6.x-4.6-beta1 and let me know if this problem is still present.
Comment #7
Jorrit commentedClosed because of lack of response.