Closed (fixed)
Project:
Audio
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
22 Sep 2008 at 15:14 UTC
Updated:
14 Oct 2008 at 02:35 UTC
I just created some content on my site for my calendar. I DID NOT have Audio File Type / getID3 file type enabled or selected for this particular content type. But this error was thrown anyway ?
* warning: Invalid argument supplied for foreach() in /Library/WebServer/Documents/mysite/www/sites/all/modules/audio/getid3/audio_getid3.module on line 294.
* The following errors where encountered while reading the file's ID3 tags:
o Could not open file ""
* warning: array_merge() [function.array-merge]: Argument #1 is not an array in /Library/WebServer/Documents/mysite/www/sites/all/modules/audio/getid3/audio_getid3.module on line 314.
* warning: array_merge() [function.array-merge]: Argument #1 is not an array in /Library/WebServer/Documents/mysite/www/sites/all/modules/audio/getid3/audio_getid3.module on line 316.The getID3 module seems to be configured correctly as there are no errors throw in the management of it, nor in the Audio module.
But again, I was attaching an audio file to this content type or anything related to Audio / getID3
Comments
Comment #1
robloachComment #2
Jeremy Toaster commentedSorry, typo
"But again, I WASN'T attaching an audio file to this content type or anything related to Audio / getID3"
Comment #3
pbarnett commentedSee http://drupal.org/node/273942#comment-1020928 for a quick fix
Comment #4
Jeremy Toaster commentedThanks,
The error goes away if I "UN"check getID3 module part of the Audio Module.
I'll just not use this module until it is fixed properly, not a fan of the "patches" :)
Comment #5
drewish commentedshould be fixed in the current -dev release. make a backup of your files and database before updating.
Comment #6
drewish commentedwhoops, sorry posted that on the wrong issue. it's still totally broken.
Comment #7
drewish commentedum, i was right the first time. this should be good okay in the -dev release.
Comment #8
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.