I have getID3 library installed and Home » administer » settings: audio, getid3 confirms it (the path is valid, there's no error mesage and the version number 1.7.7 is shown).
However Home » administer » settings » content types: 'blog entry' content type complains:
"The getID3 library used by the audio module to read and write ID3 tags does not appear to be configured correctly. The site administrator will need to check that it is installed and that the audio module knows its location. The audio_attach.module will not function without it."
I installed getID3 only AFTER I got the error from audio module setting page so I guess the error status is still remembered somewhere, any ideas where and how to reset it?
(looked at FAQ, searched drupal site, audio module bugs, found nothing relevant)
system:
- debian unstable
- php5
- mysql 5
- drupal 4.7.3
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | audioId.txt | 1.43 KB | zasran |
Comments
Comment #1
drewish commentedCan you confirm that you're running a recent (say last week or two) version of the module's 4.7 branch?
Comment #2
zasran commentedYes, using very recent version, downloaded it two days ago: Sep 24 17:45 audio-4.7.0.tar.gz
I attached list of cvs $Id for files in audio module directory so that you can check exactly which files I have.
Comment #3
drewish commentedyeah that's new enough ;) i just wanted to make sure you didn't have some wacky old stuff. rereading your error message it's clear that it's a problem with the audio_attach module in contrib. i'll work up a fix. in the mean time just disable the module.
Comment #4
drewish commentedokay easier than i thought.
Comment #5
zasran commentedAny ideas when will this be released (approximately) or how to make it work?
Comment #6
drewish commentedthe fix is committed (hence the change from active to fixed). drupal.org rebuilds packages automatically a couple of times a day. so, by now, you can download the audio module file and you'll get the fixed version.
Comment #7
zasran commentedThanks a lot! I didn't know the modules are updated all the time. Re-downloaded, re-installed and now it works! Even have a proof: http://zasran.com/drupal/?q=node/3 :-) Guess you can close this bug.
Comment #8
(not verified) commented