two screen shots.
first one, shows the file_managed table.
http://alphex.com/z/file_managed_table-20120622-150431.png
As you can see, the first few files added have the 'filename' matching the URL id values. these are the same numbers you can find the videos behind, if you went to vimeo.
Skip forward a year... the client wants to add new movies to their site...
And its generating an error.
http://alphex.com/z/file_managed_table2-20120622-150641.png
As you can see, the 'filename' is somehow getting the actual NAME of the video, and saving it in the filename field, instead of the video ID.
I have upgraded to the latest beta5 of the site in the last month or two, from what I was using a year ago. (not sure what version was out then).
This, SEEMS to be a media_vimeo issue, but I'm just guessing. Thoughts?
I'm about to go rewrite all of my themes processing to use the vimeo ID in the other field now... (ugh)
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | file_managed_table1.png | 35.26 KB | alphex |
| #1 | file_managed_table2.png | 13.96 KB | alphex |
Comments
Comment #0.0
alphex commentedFixing bad URL's to images linked.
Comment #1
alphex commentedattaching images appropriately here.
Comment #2
RobW commentedCheating here with a straight repost from the Media: YouTube queue:
For most users having the file entity's name as a human readable title is more useful. The change was made back in this issue: #1368714: Set $file->filename as video title (I'm sure there's a similar issue for Media: Vimeo). You still have the video_id variable if you need it, which isn't as readily available as a database entry but should be with some custom coding.
There probably should have been a warning when upgrading between alpha/beta versions when this was changed, but things like these happen with code in development. One of the reasons I'm trying to move towards a stable as soon as possible.
Comment #2.0
RobW commentedfixing URL's again...