I just installed and enabled this module as the latest Openlayers dev seems to require it now. After enabling it the website went unusable. I get this error:

Fatal error: Call to undefined function libraries_detect() in /home/sideoffc/public_html/sites/all/modules/proj4js/proj4js.module on line 14

How to fix this?

Comments

cesareaugusto’s picture

Anyone may help? All my websites went unusable, I got this Fatal Error blocking every page...

augustus.kling’s picture

The modules in use are clearly labelled as development releases that are not to be used on production sites. Please note that its your responsibility when you break your sites by using development releases.

Regarding a solution, please do a full text search in your Drupal folder to see if a function libraries_detect is defined somewhere. If it is we would be missing an include, if not it is likely that our dependency on the libraries module is not specific enough. Please report the version of your libraries module.

cesareaugusto’s picture

Thanks for replying augustus.kling!

The only dev module I'm using is OpenLayers, which seems to work.

I got Libraries 7.x-1.0 on. I installed Proj4JS 7.x-1.1 as it seems OpenLayers now requires it.

Pol’s picture

Status: Active » Fixed

Dude, you need Libraries 2.x...

augustus.kling’s picture

Status: Fixed » Active

Do I get this right that this means proj4js.info is wrong then? It just states any version of libraries is fine.
According to http://drupal.org/node/542202 one should be able to specify versions as well for the dependencies.

cesareaugusto’s picture

I upgraded to Libraries 2.x and the error desappeared! Thanks Pol!!!!!

Pol’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

4kant’s picture

Same here:
needed Libraries 2.x.

sa3z’s picture

Upgrading to Libraries 2.x fixed it for me too.

augustus.kling’s picture

Commit 9cf0bfa328ff0010de5643ce5a41036877f37878 requires libraries version 2 so that having the wrong version of libraries becomes obvious.

Pol’s picture

Oh nice, I didn't knew that trick :)

barbank’s picture

Correct! I had the same problem, but only when I ran the update script. I upgraded to the latest version of Libraries (7.x-2.1) and I no longer have that problem. Thank you.