as of version 3.x-dev, the urls listed in RSS feed enclosures point to the original videos files. with Drupal's private files, this would be e.g.: http://example.com/system/files/videos/original/videofile , and this url generates a 404 error.

i'm not sure what the thinking is in pointing to original files, but either the enclosure should point to the transcoded files instead (which don't generate a 404 error when using Drupal's private files), or there should be a permission/authentication hook to allow users access to the original files.

and i'll say it again: thanks for your work on this great module!

Comments

jbrown’s picture

jbrown commented
Assigned: Unassigned » jbrown
Status: Active » Closed (works as designed)

Have you tried the latest 5.x-3.x-dev? RSS feeds with private files works fine.

The thinking in pointing the RSS at the original files is to provide the highest quality video, e.g. for viewing on a TV. itunes can't even play flvs anyway.

In the future you will be able to configure multiple transcodings and set which transcodings are used for which purpose.

File access control for private files could also be a useful feature.

arh1’s picture

arh1 commented

i'm seeing the 404 errors for the enclosure files on a simple test site using private files and OpenPackage Video 5.x-3.x-dev (2008-01-25).

so are you saying the 404 errors are to be expected in the absence of a separate file access control? (RSS feeds w/ private files may be a bit of an odd scenario, i'll admit, but it's one i'm contemplating ;) )

and the access control would (like the "download audio" access control for the Audio module) essentially poke a "public" hole through Drupal's private files?

if that's all correct, i'll move this over to the openpackage.biz forum for discussion as a feature request.