Javascript client-side check fails for OpenLayers 2.12 and 2.13

I was having a similar issue where openlayers couldn't find my client-side library. My situation might be a little different, but essentially, I didn't have a folder (in my case a symlink) called "openlayers" in the sites/all/libraries folder. I had "OpenLayers-2.12" for example, and the openlayers module wasn't finding it.

I just downloaded OpenLayers for the first time, and am receiving the same error message when I try to use OpenLayers 2.12 or 2.13. I'm not having any luck with 2.12 either.

try to rename the folder in "openlayers" and check if all relevant subfolders are inside.

Yes. You don't need the internal library at external source.
My post#5 was related to the internal mode.

version 7.x.2.0 beta 7. Installed internal version 2.12 via drush. Got the error. Changed to internal and 2.12, 2.13 = no luck. External 2.11 seems to be happy. Something's not making the connection.

I'm having this problem with 2.0 beta 9. Tried all the versions down to beta 1 with same problem.

I have the same problem with 7.x-2.0-beta9. Is there any one a solution?

I had this same issue with 7.x-2.0-beta9. I downloaded the OpenLayers library again with Drush as recommended and the error message is gone and it recognizes the library.

I found that the update altered my views fields by enabling some labels that were previously disabled. When I disabled the labels in my openlayers view that had been enabled by the update that fixed a javascript issue for me.

Hi,

Indeed, quite a lot of changes has been happening in the openlayers_views module, a better handling and rendering of the fields.
You can now have all the goodness of Views fields rewriting in your popups ;-)
Don't forget to disable the labels of course if you want to, and also, in the settings of the OpenLayers Vector Data Overlay, you can select which fields to render be enabling them with a checkbox, this can reduce considerably the size of a page for your visitors and fasten the website.

I will close this for now, feel free to reopen if needed.

@jc_sed8d
I was having similar issues until I realized there are different types of downloads, a repository download which is missing required files and a release download with contains additional files that get built when the release is created. See my answer here: https://www.drupal.org/node/2233591#comment-9151119.

Hope that helps you resolve your issue, and if so, please mark this issue as fixed.

Same problem. Can use all of the debug, light mobile, except the regular release. 2.13

Hi guys,

Thanks Pol for staying with this issue: seems like a simple configuration thing that is actually really important as it stops people cold if they can't get it to register the local library. We are having the issue of:
(local) original=fails
(local) original-debug=succeeds
(external) library=succeeds

I saw some of your other posts where you used drush libraries-list, and that was revealing.

We have OL 7.x-2.0-beta11 and use drush dl-openlayers.
The library shows up as expected at ../libraries/openlayers/*, and there is indeed a file there called OpenLayers.js << this equates to the "Original" as I understand.

However (see screenshot) when I run drush libraries-list, the openlayers section only reports: original debug, light, light debug, mobile, mobile debug

There is no "original" detected. Running drush cc all and drush cache-clear drush between drush dl-openlayers does not change things.

So....what next?

Thanks indeed!

@boabjohn,

This should be fixed in the latest dev release. Please give it a try!

Hi all,
Same Here, it's accepting all versions when I select it to internal. Im running Cartaro.
Original debug
Light
Light debug...

except the Original. Message:
"Could not find a valid library with a Javascript client-side check; Value found: 0. Please visit the OpenLayers settings page for more details."

#23 changing to the latest dev worked for me.

I"m running the latest dev and have this issue... any other advice appreciated

Updating to the latest dev appears to fix this particular problem, however now I'm seeing another issue:

Key handler, class is missing in the definition of the behavior openlayers_behavior_geofield. The behavior will be disabled.

@alibama: I was in the same struggle as well (having no access to drush currently). I finally got it to work using the 7.x-2.x dev-version (2015-Jan-11) of the module and the OpenLayers 2 v2.13 branch from GitHub (not the v2.13.1). I placed the latter in the Libraries directory so the path looks as follows: sites/all/libraries/openlayers/lib/OpenLayers.js

If I understand it right, it means, that recommended version doesn't work. Shouldn't there be an another beta version?

Some months after the issue has been raised, and looking at its history, it seems obvious that at least the combination

- 2.x
- Geofield
- OSM
- no CDN
- aggregated

is no longer pursued by the maintainers. I can follow this (OL3 is now current), however, if the 2.x branch is no longer working in a fashion some (like I) might expect, I suggest you cease support for it or clearly point out that this is no option for those wanting to host the library on premises (without CDN).

Most site builders do not seem to have an issue with CDN hosted stuff, or with the drush download option. I do, since I like to inspect as thoroughly as possible any piece of source that enters our repos (at least by signature, certificate and considering the actual source). Thus, please add some clear label or something on the module page, indicating that the said approach is (currently) not available in order to save people time before they start installing all the dependencies. Or simply cease support for the 2.x branch.

No offense though, just an attempt to give an additional (non-)use-case insight. Thanks for reading.

Overall, I have tried many combinations with this. The only resolution I had was to downgrade to OpenLayers 2.11 which appears to work without issue.