Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.i've installed the media module into:
/var/www/html/drupal_cvs/modules/opt/flexinode/contrib/media
i keep all non-core modules in opt in order to manage upgrades.
i installed the proper version of getid3 in a subdir of the above.
after going to admin -> settings -> media, i get an error that getid3.php can't be found. i'm not given the option to configure it.
i hard code the path into media.module and can now see settings -> media.
i try to configure the correct path to getid3.php but it is rejected each time i submit and defaults back to 'modules/media/getid3/getid3.php'.
furthermore, there should be a note of explanation as to what this path is relative to. i'm assumming it's relative to docroot, but i could be wrong, and it should be explained near that text field.
i'll be keeping an eye on this module. i'm looking for something like this. i think a lot of drupal users probably are.
no offense, but i'm super uber wary of third party modules. mostly because they tend to get abandoned or ignored for long periods of time, whereas the core drupal code seems to be pretty well maintained.
would be nice to see a "formal" 4.6-beta release (tag) of this module that some of us could help test. i'm part developer and part tester (professionally). i don't like to test HEAD versions of anything :)
Comments
Comment #1
robertdouglass commentedI'm a little confused on why you installed the media module here:
/var/www/html/drupal_cvs/modules/opt/flexinode/contrib/media
It is possible that the path assumes that the media.module file will be found in modules/media/.
As for your suspicion of contributed modules, this module has been ignored (by me) almost since its inception, and I'll be the first to admit it. Considering the projects that I'm currently working on, finding time to maintain this properly is unlikely, plus I have reservations about the architecture and implementation. It isn't nearly modular enough to suit Drupal's media needs in the long run. This module will never make it into core as is.
That said, there is a lot of good code inside of it, and the hook_file that it introduces (the patch that had to be applied) is a good idea that I would like to see get applied to the core upload module.
Comment #2
harry slaughteras far as i know, there are no existing limitations as to where module files go, except that they have to be in the ROOT/modules directory.
that being said, i'd assume that the following would be acceptable:
/var/www/html/drupal_cvs/ - docroot
modules/opt/ - where i put all third party modules (so i can maintain core updates more easily)
flexinode/contrib/media/ - path adopted from existing CVS structure
getid3/ - makes sense to put in the directory that requires it, though this lib might better be located in ROOT/includes
i'm all for experimentation within CVS. but i do have a bit of an issue with the fact that so many modules appear on the modules page when they're actually in alpha or beta state.
there currently seem to be only two versions of drupal and contrib items: release (ie 4.6.*) and cvs head. afaik, there are no test releases (ie 4.7-rc1 or 4.7-alpha). and also afaik, there is no schedule for releases (such as with FC: http://fedora.redhat.com/participate/schedule/).
as i look at existing options for features i'm looking to add to my site, it's up to me to determine whether a given module is in a prod-release state and whether it looks like that module has not been abandoned.
so far, all the multimedia stuff i've looked at is in either a beta state or abandoned.
anyway, this is an inappropriate thread in which to author a rant, but i couldn't help myself ;)
Comment #3
robertdouglass commentedNo arguments with your assesment of the versioning system, though you should be aware that 4.7 is about to go into a code freeze, which represents a pre-release version for testing. Contrib modules, however, have absolutely no versioning organization other than the point release CVS tags (4-6, 4-7 etc.) In its defense, the media module claims to be beta code, not production code, and it is not available as a download from within the context of a stable Drupal version.
I suggest you check out the audio module that someone checked into CVS 20 minutes ago. It seems fresh enough to test your tolerance for cutting edge in a very healthy way :-)
PS - Moshe Weizman has also been fixing bugs on this module lately, so don't give up on it yet.
Comment #4
harry slaughteroh, i'm far from given up on media.module. seems like a very good start.
worst case, what i'd probably do is "borrow" your code and see if i can get it to behave the way i want. if i did so, maybe i could ultimately kick back whatever i came up with. i think the greatest risk to drupal that of everyone splitting off and doing the same thing in different ways. it would be really cool if there were a way to get folks to work together on a common interest (like mp3 || multimedia presentation). there's already a split in the filemanagement modules.
i prefer simplicity and stability over features. but one thing i want to be able to do is to "attach" media information to arbitrary nodes. say i want to show an audio clip along with my custom "Baz" node type. maybe i want to show length, artist, whatever and an m3u link.
but i don't want all media restricted to any single context.
one of the apparent weaknesses in drupal is the ability to customize pages with arbitrary content like images, audio, whatever. maybe i'm wrong about this (new to drupal). the drupal team has done a great job at creating a very generic framework. because of this, i think it's much more flexible than other similar CMSs. but in maintaining this genericness (a good thing), maybe a bit has been sacrificed in the way of depth of features. for example, upload.module works fine, but it doesn't do much, and it has some major drawbacks. seems like some of the concepts that have been explored in modules like flexinode and filemanager (and media.module:) might be integrated into the core, as they are not really specialized features so much as extensions of existing drupal features.
damn, i went off on a rant again, sorry
Comment #5
robertdouglass commentedNo problem with rants! There is actually a thread in a forum (better place for this discussion) that describes what I see as a possible path for Drupal and media files.
http://drupal.org/node/28667
Comment #6
robertdouglass commentedThe media module is officially unsupported. Pending anyone taking a strong interest in it and volunteering to become its maintainer, it will eventually be removed. Let me know if you are interested in adopting it.