I'm testing with a mp4 video file, if I select VideoJS as player for .mp4 files under Video module configuration the rendered drupal page contains

<div class="field field-name-field-video field-type-video field-label-inline clearfix">
   <div class="field-label">video:&nbsp;</div>
   <div class="field-items">
      <div class="field-item even">
         <!-- Begin VideoJS -->
         <!-- End VideoJS -->
      </div>
   </div>
</div>

So no video at all and I also receive these errors:

Strict warning: Creating default object from empty value in video_helper->video_object() (line 40 of [...]/modules/video/includes/video_helper.inc).
Notice: Undefined index: filemime in template_preprocess_videojs() (line 38 of [...]/modules/videojs/includes/videojs.theme.inc).
Notice: Undefined index: filemime in template_preprocess_videojs() (line 38 of [...]/modules/videojs/includes/videojs.theme.inc).
Notice: Undefined property: stdClass::$uri in file_validate_is_image() (line 1688 of [...]/includes/file.inc).
Notice: Undefined offset: 0 in template_preprocess_videojs() (line 78 of [...]/modules/videojs/includes/videojs.theme.inc).

I'm using video-7.x-1.0-alpha2 and I've tried with videojs-7.x-1.2 and videojs-7.x-dev with the same result

Comments

thomasflad’s picture

thomasflad commented

+1

ranavaibhav’s picture

ranavaibhav
Location Toronto
commented

having exact problem, however with .mp3 files

breidert’s picture

breidert commented

I had the same problem. I solved the issues of displaying the node by configuring the corresponding field for video upload.

In "Manage fields" (admin/content/node-type/[type-name]/fields) the field type is set to file, and the form element (for uploading) is set to video.

However, in the settings for "Display fields" (admin/content/node-type/[type-name]/display) the field display for "Teaser" and "Full node" is set to VideoJS and NOT video.

I hope this does not break other workflows in the video module (trancoding, S3, etc.)

Elder Brother’s picture

Elder Brother commented

Same issue, though trying to get around it by specifying VideoJS as the display field doesn't suffice, as I have a fall-back flv file that should open with Flowplayer, which is no longer triggered.

loominade’s picture

loominade commented

subscribe

greg.harvey’s picture

greg.harvey
Primary language English
Location Occitanie, France
commented

Same here (Drupal 6 version...) - still hunting for a fix.

ZuluWarrior’s picture

ZuluWarrior commented

Sub,

I am using the Media Module to handle my media files, so my field type is multimedia asset not file, but I get these errors when I edit the node, and of course no video displayed...

ZuluWarrior’s picture

ZuluWarrior commented

FYI,

I got this working with a standard File Field using the solution above, which is included in a patch file here: #1184152: 200 error stream not found

Still haven't got it working with the Nedia module yet though (causes the above errors)

Ammendum: Have got this working with Media module, you need to select a File field type, and select File Seelctor as the widget, this allows youto upload and select with the media file selector and manage multimedia resources with Media module (still needs the patch mentioned)...

goldlilys’s picture

goldlilys commented

@ #8

Got it working with Media Module too when uploading videos. But why would VideoJS not play videos coming from Youtube or some external site ? It doesn't make sense to create 2 video fields to upload videos AND post external video like YT.

and this error is still showing up:

Notice: Undefined offset: 0 in template_preprocess_videojs() (line 78 of htdocs/sites/all/modules/videojs/includes/videojs.theme.inc).

ZuluWarrior’s picture

ZuluWarrior commented

Perhaps VideoJS does not properly handle the file type string that media provides? THis string is stored in the database and is different for youtube videos (video/youtube) and uploaded media (video/TYPE)?

Just a quick thought...

Jorrit’s picture

Jorrit commented
Status: Active » Fixed

This error occurs because the Video.js module expects a filemime key in the item array.

I have added more checks to the theme code to handle this situation without notices.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.