Posted by spiffyd on December 1, 2008 at 11:53am
Jump to:
| Project: | FlashVideo |
| Version: | 6.x-1.4 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Videos that were working before now now show the "Video Not Available" image after overwriting module with latest rc2 update (and running cron and update.php).
Any suggestions?
Comments
#1
Has anyone else seen this error?.... This would be rather severe if that is the case. Spiffy, I am curious how you are utilizing the FlashVideo module as to why you saw this error.
#2
I haven't seen this in any of my testing with 6.x-1.4-rc2.
#3
I am going to assume that this is not an issue. Spiffy.... I would like to take a look at what happened before releasing version 1.4.
#4
Travis,
I spent an hour checking out the issue thoroughly and confirmed my findings (I can replicate this on my set up).
On my particular set up, rc2 makes all my videos show "videos not unavailable". The moment I overwrote my Flashvideo module directory with rc1 or earlier versions makes everything work normally again.
I'd like to note that my video nodes were all created via video import and the "[video]" tag is not written in the "Body field" but rather a custom CCK text field so there may some issues with other modules such as CCK.
However, I will do more debugging and beta testing by trying to replicate this issue on a fresh Drupal 6.x install.
Denis
#5
Denis,
I have just made considerable fixes to the Video Import for the latest release. I am very confident that what I just committed to CVS will fix your issue. Particularly, I found a significant error where the import was not working for the FLV files in the video import directory.
To confirm my suspicion, will you open up your database and look at the files tables.... and see if the filemime value is blank for the FLV files that are not showing? Then, edit those and add application/octet-stream as the mime type and then see if they show up again?
If this works, then my suspicion is correct, and I am getting VERY close to a stable 1.4 release.
Thanks everyone for your efforts!!!
#6
Denis,
I have done numerous tests and cannot reproduce this.... Also, the videos on your site are working just fine. Setting status to closed.
#7
The videos are fine because I downgraded to rc1. For some reason I cannot access my site b/c my host may be down at this moment.
If no one else is having this issue, I suspect it may be a conflict with another module or something else specific to my set up. I'll continue to investigate... don't let this stop you from releasing 1.4.
Thank you for your prompt replies!
Denis
#8
Travis,
My host is finally back up. I took a look at the files tables, but all of the filemimes for the FLV files are showing flv-application/octet-stream so that is not the issue...
#9
Travis,
Upon closer examination of #5, I just noticed you mention that the filemime should be "application/octet-stream". Did you mean "flv-application/octet-stream" because that's what mine are listed as...
Denis
#10
Travis,
So after playing with the new 1.4 some more, I made a few discoveries...
1) I did a fresh Drupal install and 1.4 works fine without the hitch.
2) As mentioned, all my video nodes which were created with Flashvideo legacy versions before rc1 do not work. I will have to reimport/recreate all the nodes with 1.4 to make them working again. Perhaps this has something to do with new features such as the special filenaming scheme 1.4 has that older versions do not... Not sure if there's any easier way (such as making modifications to the database tables) for me to do this! It will take so much time because there are other fields associated with each video node I need to recreate... :(
3) Originally, I enable video thumbnails via Custom FlashVars (under Flash Player Settings in config) by using image=@thumbnail.
With legacy versions, the FLV filename is whatever name the file had upon import (no #'s were appended at the end of the file name). So all I had to do to enable a video thumbnail for that particular video file was to put an image file with the same file name as the video file in the video output directory.
For instance, if my video was called "demo_video.flv", I would put a JPG called "demo_video.jpg" in the output directory and with the proper FlashVars settings, I get the video thumbnail.
However, this does not work in 1.4 (and rc1-2) because the module tacks on num1bers on the file name. See http://drupal.org/node/343097 for explanation/discussion.
I have to manually rename every single file and add the same appended number to the image file name to make the thumbs work. So for instance, the video may be called "demo_video_603.flv". The thumb has to be named "demo_video_603.jpg" to work.
4) Can you clarify how do I use the new feature: "The import feature now allows more than one node type to import."? I assume you have to specify a different import directory under Flashvideo settings foreach node content type?
Thanks!
Denis
#11
Denis,
Thanks for your comments. They are very valuable.
To answer your question about the importing changes... I made a change with version 1.4 where you can now provide different import directories for each different node type. This is much more powerful than the previous version where only one import directory can be provided. I added this because many people are using my module for importing and creating Audio nodes on the fly (which actually works), and this would allow you to provide an "audio_import" directory which would create "Audio" nodes, and a "video_import" directory to create "Video" nodes. This also allowed me to remove the node type selection when defining the import directory (which was pretty kludgey I thought ).
Thanks,
Travis.
#12
I've somehow managed to pinpoint the cause of the problem to be the File Framework module.
See my analysis and partial solution here: http://spiffyd.com/blog/bug-fixed-file-framework-prevents-flashvideo-nod...
I am still looking for...
1) A solution to making video nodes made with FlashVideo 6.x-1.4-beta-6 or earlier work with the latest v1.4 without having to recreate all the nodes.
2) A solution to making FlashVideo v1.4 compatible with File Framework.
#13
I resolved my issue - well, kinda - as everything works now on both the latest FV and FF versions.
Here's how I did it: http://spiffyd.com/blog/bug-fixed-file-framework-prevents-flashvideo-nod...
My condolences to ANYONE that has many video nodes created with FV beta 6 or earlier and would like to upgrade to 1.4 and are encountering issues like the one here.
#14
Awesome work Denis! Thanks for everything on this.
#15
Automatically closed -- issue fixed for two weeks with no activity.