I'm running the latest version of 5.x-2.x-dev, and whenever I try to add new audio, I get the following errors. It doesn't happen with the admin account -- only with other users, and happens only when adding, and not when editing (replacing with a new MP3). Any ideas what might be wrong?

Thanks

* warning: Invalid argument supplied for foreach() in /mypath/modules/audio/audio_getid3.module on line 432.
* warning: array_merge() [function.array-merge]: Argument #1 is not an array in /mypath/modules/audio/audio_getid3.module on line 453.
* warning: Invalid argument supplied for foreach() in /mypath/modules/audio/audio.module on line 1693.

Comments

pgi’s picture

pgi commented

Up
I've got the same problem with the lastest version of 5.x-2.x-dev

drewish’s picture

drewish commented
Status: Active » Postponed (maintainer needs more info)

marked #261877: Problem with the GetId3 in the latest 5.x-2.x-dev as a duplicate.

i can't seem to replicate it... created a test user, granted them permission to create audio nodes, uploaded an mp3 with id3 tags and it worked fine. the errors look like there's no value set on $node->audio_tags when the node is being saved.

tj2653’s picture

tj2653 commented

Hi drewish,

Let me know what details you would like. I have the same workflow as you. Running Drupal 5.7.

Thanks,
tj2653

trevorleenc’s picture

trevorleenc commented

I too am having this problem...

warning: Invalid argument supplied for foreach() in /nfs/c03/h03/mnt/55341/domains/filmblazer.com/html/sites/all/modules/audio/audio_getid3.module on line 431.
warning: array_merge() [function.array-merge]: Argument #1 is not an array in /nfs/c03/h03/mnt/55341/domains/filmblazer.com/html/sites/all/modules/audio/audio_getid3.module on line 452.
warning: Invalid argument supplied for foreach() in /nfs/c03/h03/mnt/55341/domains/filmblazer.com/html/sites/all/modules/audio/audio.module on line 1693.

I have the following 'relative' setup:
drupal 5.19
audio 5.x-2.0-beta1
cck 5.x-1.10
token 5.x-1.13
views 5.x-1.6

this 'seems' to have started happening around the time I upgraded core and some of the modules, but my client did not let me know about this issue until now.

as with the other statements, admin can post audio content types with no problem, but anyone with permissions cannot.