getID3 causes WSOD for administrator page

Check your PHP memory limit at admin/reports/status -- you might need to increase the available memory as described at http://drupal.org/node/207036

subscribing

You've got to check your PHP error log. There's a fatal error that's causing the white screen. It should provide a message with a file name and line number where the problem occurred.

I renamed/copied ...getid3.write.php to ...write.php (I now have both)
It is now enabled, have not tested.

I just had this one - and its cause was obscure!

Hi, I'm a newbie at Drupal, and lovin' it! :-)

Using Firefox 3.6.13 on OS X 10.6.5 (on 5 year old MacBook Pro), I downloaded getid3 1.8.2 from the official site. Untarring, etc, it gave me a folder: getid3-1. All the files had "getid3.something.php" (.txt) for their names. Nothing, obviously, about getid3 would work. There wasn't any "top" level getid3 folder. (See the picture; I've since named the folder "oldgetid3"; I was just about to delete it when I saw this in the "Recent Issues" column.)

Eventually I decided to try downloading the getid3 zip file using Safari. That worked! I had the right folders, the demo folder (which I deleted), and the getid3 module found everything - after I'd put the trailing "/" back! (It wanted "sites/all/libraries/getid3/getid3/"; in my 'research', I'd altered it to "sites/all/libraries/getid3/getid3".)

I don't know why, but it seems that the Firefox downloader does something wrong with the zip file; all is well when I downloaded it with Safari. I tried the "Open" and "Save" commands on Firefox, and both do the same thing. I'm not surprised, but I thought it worth checking!

As I said, it was all a little obscure - I couldn't figure out what was supposed to be in the getid3. (Mostly because I couldn't find a screenshot or listing of what should be in the folder! I've rectified that. :-) The bad_getid3 shows what I had; the good_id3 image shows what you should have.) I should note I've not tested getid3 v1.8.2; I've just downloaded and spent an hour or two trying to get it to work!

So if you have a white screen, it might be the downloaded version of getid3.

Carolyn Ann

(Just a quick update: I had the same problem with CKEditor as well! I will report it to the Mozilla folks.)
(Edited: I changed "but" to "and"...)

I was getting the White Screen of Death on the main "Administer" page: ...drupal/admin. Began to uninstall modules until I found which was responsible. Turned out to be getid3(). I just read the post by Carolyn Ann at http://drupal.org/node/702456 and will have a look if I set it up incorrectly. Thanks Carolyn Ann.

Cheers,

DaFreak

OK I get the problem. Its not with Firefox. The link on the getid3.org site points to a page where two separate files are listed. One is 97K the other is 456.4K. Download the 456.4K one. Its easy to make this mistake when you are in a hurry. Something about the way it is displayed on SourceForge. The 97K one is in bigger type, whereas the 456.4K one is bolded but smaller type. I guess some of us tend to dive in to the bigger type. Must be the "bigger is better" mentality. ;-) Well in this case bigger is better, but file size not appearance.

Hmm, ok, installed it but still getting WSOD when I go to /admin or the getID3 admin page! dammit... I'll figure this out. getid3() what a pain in de ass module you are!

Carolyn Ann, you didn't say where you put the "/". Is that on the getid3 config page? I can't seem to get to it. WSOD :-(

Ok in the continuing saga of the getid3() WSOD...

I actually read the install instructions this time. I guess that helps. The getid3 files go in the sites/all/libraries directory. Not in sites/all/modules/getid3! Did that and boom!... No more WSOD on admin page. Yaay.
But hold on... its not over... "The getID3() module cannot find the getID3 library used to read and write ID3 tags. The site administrator will need to verify that it is installed and then update the settings." Ok so I go to the settings page. Aha here is the problem. The default directory is set to "sites/all/libraries/getid3" whereas it should be "sites/all/libraries/getid3/getid3" because the files it is looking for are in this subdirectory, if you followed the instructions in the install.txt. Ok so I change the directory to "sites/all/libraries/getid3/getid3/" ...remembering what Carolyn Ann said about the final slash. Submit and... WSOD!! dammit! Try to go back to settings page and... WSOD! double dammit!! Now how the ~bleep~ do I go back to remove that trailing slash and try again?!

Stay tuned to the trials and tribulations of
DaFreak

Also this module was causing the dreaded "http error 0" when combined with CCK FileField and ImageField. No luck getting it to work, even upon disable/reenable, uninstall/reinstall. I am uninstalling this module for the time being! :-P

-Freak Out!

I had similar WSOD issues, until I realized that I was using the wrong version of the library. =P

Try these steps:

1. Install and enable the getid3 module.

2. Within <root>/sites/all make a new directory and subdirectory :

libraries/getid3

3. Download and extract the getid3-1.7.9.zip to the getid3 subfolder.

4. Enter the following path into the getid3 admin settings and click the Save configuration button:

sites/all/libraries/getid3/getid3/getid3

I had to click Save configuration twice to get rid of the error messages.

Just to add to what lmjr just posted, you need to go to this page to get version 1.7.9. The main getID page (http://www.getid3.org/) has a link to 1.8.3, which didn't work for me.

As far as I can see, if you follow the modules instructions you don't need to change the default path at /admin/settings/getid3. It can stay as: sites/all/libraries/getid3/getid3. I'm assuming you've already created /libraries/getid3/ so once extracted write.php is at /libraries/getid3/getid3/write.php.

Thank you! v1.7.9 did it for me on the first shot.... I too thought the "newer" version would be better but come to find out not even the Guru's and the Spook's like the new release :)~ TY again

One thing of note is that if you are using a PHP version < 5 than 1.7.9 is still required as it retains PHP 4.x support.

Just seconding (or thirding!) the solution of using version 1.7.9 for Drupal 6. I tried several times installing and reinstalling with version 1.8.3, and got the WSOD every time when I went to the settings page. Found this thread, downloaded and installed version 1.7.9, and it worked first time, no problems.

I believe that worked for me too. Thank you all! Apologies for previous freakout. :-)

Marking as closed since users seem to be getting this set up correctly now. I've deployed the module on 3 sites without issue.

Original isssue seemed to be from a WSOD.