We have an Amazon S3 server set up, and are using Zencoder to encode our videos for us. Everything is working in this respect (including getting the videos to display on an iPhone, iPad, etc...). Unfortunately, when our users attempt to delete or edit a video, we have serious issues come up.
The user can remove the old video, and upload a new one, and even choose a new thumbnail image for their video. Unfortunately, as soon as the node is saved, problems occur. Looking in the database, it seems that the database line for the particular video is corrupted (sample entry: jobid - 0, status - 1, completed - 0, data - null, other fields - normal). I'll update this issue with information about what was received on the Zencoder side (to see if the new file actually got transferred to Zencoder properly).
Any suggestions for other debugging information that will help you?
Comments
Comment #1
Jorrit commentedAre you sure you use version 4.2? Have you considered upgrading to 4.7?
Comment #2
dwees commentedTesting upgrading to see if it fixes the issue. We've had a different issue with the upgrade (see #1394268: Incorrect URL to file after upgrade from 6.x-4.2 to 6.x-4.7) and once that is cleared up, I will update this bug report.
Comment #3
Jorrit commentedHave you had the time to retest this issue with 4.7, now that #1394268: Incorrect URL to file after upgrade from 6.x-4.2 to 6.x-4.7 has been closed?
Comment #4
dwees commentedNo, not yet. I did one test and it failed, but I think the test was not "fair" so I need to recreate the appropriate conditions, and rerun the test. I'll get back to you within a couple of days.
Thanks for being so responsive. :)
Comment #5
Jorrit commentedHave you been able to reproduce this issue?
Comment #6
dwees commentedI tried upgrading to the newest version of the site (on our staging server) and now the S3 video / Zencoder chain is broken for some reason. I've got to get that working first, and then I'll get back to you. I'm not sure why it isn't working, but another developer set it up originally, and I'm waiting for him to trouble shoot first.
Comment #7
Jorrit commentedAny result?
Comment #8
Jorrit commentedClosed because of lack of response.
Comment #9
dwees commentedSorry, I don't know if we resolved this or not, but I'm no longer working on this issue myself. Another firm has taken over development. Thanks for your patience.