"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."
I everything from INSTALL.txt - downloaded and put http://sourceforge.net/projects/getid3/files/getID3()%201.x/1.7.9/
grant all permissions to folders and files but still have that message and the module doesn't work.
any ideas how to make it working?

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

hartt96003’s picture

I"m having the same problem even though I checked in filezilla the dir has both the needed files.

hartt96003’s picture

I'm having the same problem, checked the dir and it has both the needed files, which drupal keep saying aren't there. Looking for solution now.

mcrickman’s picture

I had the same issue but after reviewing the install file I correctly installed the library. Try reviewing the install file located in the modules directory.

hartt96003’s picture

what does it mean to review the install file? thanks for your time!

JaDrupal’s picture

I have the same issue.

Cayenne’s picture

Same here. Certainly willing to believe it's my fault because I had the same problem with jquery ui, though there was a module bug ultimately at fault

here is the path to the php file: /var/www/sites/all/libraries/getid3/getid3/getid3.php
"owner" is "www-data" just like the drupal files.

Arrgh. any magic bullet is welcome

EDIT: and I carefully read and (I think) followed both the web and install file instructions

yang_yi_cn’s picture

Component: Miscellaneous » Documentation
Status: Active » Needs review

Actually I struggled a little bit with this and here is the solution:

The problem is about the permission. It's not the file itself, it's about the "getid3" directory that you extracted from the zip file. After it's extracted, it has permission 700, which means nobody can access the directory except the owner, which is the user that you just used to extract the files. So the Apache user CAN NOT access the folder, thus not able to see any files in it.

To fix it, just change the getid3 folder permission to 755 to allow read access for others.

Note this is for the "getid3" folder inside the parent "getid3" folder only.

I guess this is a issue of packing of the getid3 lib, but it will be very helpful if the owner of this module can add this information to the documentation to ask user check the folder permissions.

hartt96003’s picture

thank you so much yang_yi_cn

asb’s picture

Status: Needs review » Reviewed & tested by the community

Same issue here, the analysis from #7 is correct and fixes the problem.

This should be definitely in the installation instructions.

Thanks, yang_yi_cn!

-asb

Mohamed Farag’s picture

Category: support » bug
FileSize
42.11 KB

When tried to enable getID3 module from the modules menu in Administration area, I got this error message (see attachment).

It became enabled, and check box is dimmed.

I am running Drupal 6.19 on Linux Centos server.

Message:

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 an

deanmcinnis’s picture

I've tried every combination suggested/implied: both in the libraries folder and the modules folder; made sure 755 rwe; still can't find the library; what is the next step for making sure this is installed correctly? drupal 6 sees / enables the module; it can't find the library. My last try was in the modules folder w/ .../sites/all/modules/getid3/getid3/getid3/write.php Is this the exact file it's looking for? any ideas??? going crazy. dean

VM’s picture

Those with this issue need to report the version of the getid3 library in use. If 1.9.0 then you need the patch from #1212854: Allow getid3 module to work with version 1.9.0 of the getid3 library

Otherwise, the path to the getid3.php is dependent on how it's been extracted and how many folders deep it resides.

also of note, leave off the trailing /

Part of this issue is that the getid3 library uses the double getid3 in the path.

ie: getid3/getid3/getid3.php

I extract the interior getid3 folder, which holds the necessary files and upload it to the libraries folder. This allows me to use only one getid3 in the path settings. ie: sites/all/libraries/getid3/getid3.php

LJEsposito’s picture

You can tell sloppy work because the more you try to explain it, the more confusing it gets. No I won't tell you what version I'm using because unlike most other modules, it wasn't available within the file name. Yet another frustrating evening with drupal! I'll see if I can track down the one responsible for documenting getid3 for drupal so I can share my frustration with them too!

VM’s picture

getid3 module and the getid3 library are two different projects. At any one time they may become disconnected due to continuous movement of the library itself. It happens. Drupal.org cannot package the getid3() library in the getid3 module because the getid3() library is not GPL.

The version # of the getid3() library is indeed included in the getid3.php file as this is how drupal reports the which version is in use. The version # can be found in the const VERSION string. In getid3() version 1.9.0 which is the current stable release of the library the line # is 113. The non listing of the version # at the top of any of their files is not something drupal maintainers/supporters have any control over. Seriously though, you downloaded it from http://getid3.sourceforge.net/ thus one would figure you'd know what version you downloaded. If you don't you should.

I'd clean up the documentation myself if those who are having trouble would better explain what they are having trouble with. It's difficult to put myself in someones shoes when it works for me. Obviously I'm taking something for granted due to my experience over the years. However, not knowing exactly what I'm taking for granted is where users like yourself can aid by specifying what you are having trouble with.

There is nothing drupal maintainers or supporters can do about the library itself or its momentum.

Of note: Attitudes like yours is why users bail on helping others and maintainers discontinue contributing or tend to ignore the issue queues and requests for more documentation. Thanks for taking the time to help make something better.

VM’s picture

removing erroneous issue tag

VM’s picture

Category: bug » support
Status: Reviewed & tested by the community » Postponed (maintainer needs more info)

remarking category and status as there is no patch here to review.

LJEsposito’s picture

Thanks for your reply VM. I am not a programmer and no matter what anyone says, if you're not a programmer, you are in for a ton of frustration with Drupal. But my frustration does not give me license to be rude to those like you who are trying to help. I support a CRM app in my day job and I understand your frustration of trying to help people who refuse to provide details. I will continue to work through this issue. Is there a post where non-programmers can vent their frustrations and is there a warning somewhere that tells non-programmers to beware because they're in for rough sailing?

Thanks again,
Larry Esposito

VM’s picture

I'm not a programmer and I've no computer science schooling or degree.. Yet I've worked with Drupal since Drupal 4.7.x. Thus I find your assertion largely bogus.

asb’s picture

Status: Postponed (maintainer needs more info) » Closed (fixed)

@ LJEsposito: Please ignore the off-topic rumblings and bogus suggestions as this is a support issue and not a social chit chat.

The described issue can be fixed with the instructions in #7 which are missing in the documentation. So please check the permissions on your server accordingly.

If you installed something without a version number in the filename, it most probably isn't a Drupal module. All properly packaged Drupal modules have a file name like getid3-6.x-1.4.tar.gz, so delete the files you extracted completely and download a proper Drupal module from the project page. Take care that the module version matches your Drupal core version (6.x oder 7.x). Further step-by-step instructions are provided in the module's archive file in INSTALL.TXT. Together with the instructions from #7 this is everything you need to get this module working. It should take you not more than five minutes to get going.

Please report back if this fixes your issue, and if not, reopen and provide an exact description of the steps you made, including your Drupal core version, the operating system your site runs on, and the full paths relative to your site's root folder.

LJEsposito’s picture

So let me recap:
I was in the process of updating core and some 20+ outdated modules, a tiresome chore. The Core update from 6.19? to 6.22 went without incident, then I successfully completed the 3 or 4 security module updates and I was in the process of updating 3 outdated modules at a time. I had completed the getID3() update from 1.3 to 1.4 without incident until I updated the next 3 modules when I received the library error. I followed instructions to load the library with no luck. I found the current thread and made the needed permissions update per #7 still with no luck. I realize the modules are clearly identified but libraries are not so I wasn't sure if I had 1.9.0 as referenced in #12. Having reached my frustration threshold I simply backed out the library and the module update and returned my archived getID3() folder back to sites/all/modules. It includes the necessary library files for that module version. I do not believe I did anything wrong throughout the process. The module update instructions are incomplete, the thread is hard to follow and there is even discussion of a needed patch. Despite all this my gut tells me I had done everything correctly but the errors had persisted. I am content to leave this as an outdated module and may give it one more try later as you suggest. If that doesn't work, I'll review impact of removing it altogether. As I've done here, I'll update with my findings as they unfold.

As noted in Post #17 I would like to find a place where I can vent my frustrations. I realize it isn't appropriate in threads addressing specific issues and I do apologize for initiating and instigating the off topic comments.

Thanks for your follow up asb!
Larry Esposito

asb’s picture

I am afraid we all need a high level of frustration tolerance when working with Drupal, or Open Source Software, or any software in general. That's simply the deal with development work, so we should try to make the best out of it. External libraries are a continous source of frustration, I agree, and the libraries API doesn't make things always easier yet. However, in regard to getID3() I personally can vouch that it works without any patches, so please do not give up yet ;) (with other external libraries I have failed, so I know the feeling of helplessness and desperation very well, when documentation in incomplete or misleading, or you not even know if it even can work).

These are paths from a working installation of getID3():

sites/all/modules/getid3/ - module folder, includes getid3.info and getid3.module
sites/all/libraries/getid3/ - libraries folder, includes a *subfolder* getid3 with the actual library getid3.php

Installed versions: getid3 module (6.x-1.4), getID3() library (1.7.9-20090308) according to .sites/all/libraries/getid3/getid3/getid3.php.

The settings for the getid3 module are at .//admin/settings/getid3</a>; there is a path to be configured, and as soon as the module can locate the library there, it reports the identified library version. In my case the entered path is <code>sites/all/libraries/getid3/getid3.

I do not have the libraries API module (current version 6.x-1.0) installed on this site. In my case, the folder ./sites/all/libraries/getid3/getid3 is owned by root and has the permissions drwxr-xr-x (world-readable).

BTW: For module updates I can highly recommend the commend-line too 'drush' which makes it really easier to update modules one by one, run update.php, and keep an eye on the watchdog messages in case of errors.

LJEsposito’s picture

I followed INSTALL instructions appended below and continue to get the following Status Report Error for getID3():

You must install getID3() to sites/all/libraries/getid3, or configure its installation path.

It may be important to note a few things (other than core version 6.22)

  1. Since "you must install getID3() to sites/all/libraries/getid3" is confusing to me (which getid3) I chose to configure the installation path. I believe I configured the path correctly since I continued to get error messages in the configuration process until I got it right: "sites/all/libraries/getid3/getid3/" (with or without the trailing forward slash "/").
  2. When I run update.php and "Select versions", I get "No updates available" for all modules and there is no sight of getID3(). Modules list shows proper current version of getID3 (6.x-1.4) and prior to the update I migrated the 6.x-1.3 folder to a temporary archive that I use (my concern with drush update is that the old version is lost and I'm forced to go track it down).
  3. The latest stable library version is 1.9.1 and I was able to find it listed in getid3.php (const VERSION ='1.9.1-20110810'). I'm not sure if the new version is causing the problem but I couldn't locate 1.7.9.
  4. Strangely, this time around, I did not have to use chmod to update the getid3 folder since it was already 755

Thanks for your supportive words asb. I am working on drush but it has it's own challenges. It would be nice if someone built a module to emulate drush for those of us who struggle with CLI.

INSTALL
-------
1. Place the entire getid3 directory into your modules directory
(sites/all/modules is the usual location).
2. Create a new folder for the getID3 library at:
cd YOUR-DRUPAL-ROOT
mkdir -p sites/all/libraries/getid3
3. Go to http://www.getid3.org/ and download the latest stable version
(currently 1.7.9) into the new directory:
cd sites/all/libraries/getid3
wget "http://downloads.sourceforge.net/project/getid3/getID3%28%29%201.x/1.7.9..."
4. Unzip the contents of the zip file into sites/all/libraries/getid3/ so that
write.php is located in sites/all/libraries/getid3/getid3/:
unzip getid3-1.7.9.zip
5. Delete the demos directory:
rm -r demos/
6. Go to Administer > Site building > Modules and enable the GetID3 module.
7. Go to Administer > Settings > getID3. If you see the version you just
downloaded, the module is installed correctly.

Thanks again,
Larry Esposito

asb’s picture

@Larry: So you got it working now, right? Great!

Regarding drush, you don't need to worry about manually backing up your module directories; drush update automatically creates backups in your site's root folder (older versions) respectively in your user's home directory (current versions).

Also, there is a command drush getid3-download which can be alternatively used to install the library files (do never mix manual and downloads automated installations!)

VM’s picture

no the user did not get it working

I followed INSTALL instructions appended below and continue to get the following Status Report Error for getID3():

You must install getID3() to sites/all/libraries/getid3, or configure its installation path.

Thus the getid3() settings page is reporting it can't find the library.

Thus it is highly likely that the install can't find the library because the getid3() library version 1.9.0 is being used by the install and not 1.7.9. NOTE this is important because the way the version is set by the getID3 library has changed and it directly affects the way the libraries status is reported by the getid3 drupal module.

Hence why the version # was asked for much earlier in this thread and why I linked to the issue thread which includes a patch to correct the reporting problem with 1.9.0 of the libary.

With a google search and a little poking around on the net (5 mins) I found the 1.7.9 libraries. See: http://sourceforge.net/projects/getid3/files/getID3%28%29%201.x/1.7.9/

So your mission if you chose to accept it is to either:

test the patch in #1212854: Allow getid3 module to work with version 1.9.0 of the getid3 library (which was linked earlier)
or;
get a copy of the 1.7.9 getid3() library

Don't do both.

LJEsposito’s picture

I did neither. I tried to recover my 6.x-1.3 version of getID3 but my web provider was running an unannounced upgrade which got me into an unfamiliar file manager utility and I started getting a fatal error in administrator when trying to update the getID3() library location. Fortunately I was miraculously able to delete all getID3 folders, files and libraries, find and re-install the 6.x-1.3 version which was the only thing that I knew that worked and the 1.7.9 library to which the INSTALL instructions provided directions. But I placed the getID3 library folder in the existing sites/all/modules/getID3 folder which had worked for me in the past rather than the suggested /sites/all/libraries/getID3 folder.

I'm done with this - it was a nightmare, as are most things for me with drupal. I'm calling a moratorium on getID3 for 3 months (i.e. no further updates to this thread)! Hopefully the owners of this Module will get around to updating it appropriately by then!

Thanks to VM and asb for your attempts to get me through this. Sorry I couldn't deliver the goods!

Thanks again,
Larry Esposito

Eduart’s picture

It is very importan to read the INSTALL.TXT document of this module:

Modules/GetID3/

INSTALL.TXT (instructions):
-------
1. Place the entire getid3 directory into your modules directory
(sites/all/modules is the usual location).
2. Create a new folder for the getID3 library at:
cd YOUR-DRUPAL-ROOT
mkdir -p sites/all/libraries/getid3
3. Go to http://www.getid3.org/ and download the latest stable version
(currently 1.7.9) into the new directory:
cd sites/all/libraries/getid3
wget "http://downloads.sourceforge.net/project/getid3/getID3%28%29%201.x/1.7.9..."
4. Unzip the contents of the zip file into sites/all/libraries/getid3/ so that
write.php is located in sites/all/libraries/getid3/getid3/:
unzip getid3-1.7.9.zip
5. Delete the demos directory:
rm -r demos/
6. Go to Administer > Site building > Modules and enable the GetID3 module.
7. Go to Administer > Settings > getID3. If you see the version you just
downloaded, the module is installed correctly.