Need help with openlayers, just dowloaded .dev, dblog is floaded with - layer not found. what is the issue? thank you

Comments

zzolo’s picture

What are the actual messages? Are maps working as normal?

mefisto75’s picture

zzolo, thank you for the reply. I think this was due to me just getting to know this module. Let me further investigate - going thru tutorials right now. Will post back.

zzolo’s picture

Status: Active » Closed (works as designed)

Hey @mefisto75. Just checking in. Gonna close for now, but feel free to reopen.

biydng’s picture

Priority: Normal » Critical
Status: Closed (works as designed) » Active

I would like to re-open this issue as I am seeing the Layer not found in my newly installed drupal7.9 log messages. Whenever I visit the OpenLayers setting page (Structure>OpenLayers), there is a "Layer not found" error in the drupal log and the setting page itself display a message in a block: "Error making request to server.". The major problem is that I can not edit an OpenLayers map I created. I would first get "Page not found" upon saving and then not able to get to the edit page at all after I return to the map list page. The Apache server error log shows the following error:

**********************************************************************************
[Wed Dec 14 12:31:27 2011] [error] [client 127.0.0.1] File does not exist: C:/ApacheWebRoot/drupal79/admin, referer: http://localhost:8080/Drupal79/?q=admin/structure/openlayers/maps
[Wed Dec 14 12:31:36 2011] [error] [client 127.0.0.1] File does not exist: C:/ApacheWebRoot/drupal79/admin, referer: http://localhost:8080/Drupal79/?q=admin/structure/openlayers/maps/user_l...
[Wed Dec 14 12:32:17 2011] [notice] Parent: child process exited with status 255 -- Restarting.
*******************************************************************************************************

The Drupal log messages just repeatedly show the "Layer not found" error.

Please help. Thanks!

nod_’s picture

Might sounds stupid but you never know, have you tried clearing your cache ?

biydng’s picture

Yes, I did clear my cache from time to time hoping that the problem will go away, but the errors remain. I actually have uninstalled/reinstalled OpenLayers/clear cache many times but didn't help. The weird thing is that whenever I used the library path on my server (sites/all/libraries/OpenLayers/OpenLayers.js) the OpenLayers page will complain that the version is not the suggested version. Right now I am using the hosted library path.

biydng’s picture

StatusFileSize
new193.26 KB

Hello, anyone out there? See the attached server request error screenshot.

biydng’s picture

Version: 7.x-2.x-dev » 7.x-2.0-beta1

I upgraded to OpenLayers 7.x-2.x-beta1 and the problems are still there(had to redo the patch of fixing all the option_form incompatibility with ctools strict warnings). Can someone please offer some insights or any clues about what could be wrong? Thanks!

mefisto75’s picture

I had these issues but they go away as soon as you configure OL.

mefisto75’s picture

Note, i had no problems making request to a server. Just layer not found.

biydng’s picture

Thanks for the note. This is probably a totally different issue from the original one. I remember when I first did the OL configuration, there was no server error, though there had been a lot of strict warnings for OL conflicts with ctools. I ran all the patches necessary to fix those warnings along with other errors of other modules. All of a sudden the server error popped up. I'll continue to investigate and probably will close this one and open a new issue for my problems.

biydng’s picture

Found the code where this error is thrown:sites\all\modules\openlayers\modules\openlayers_ui\jsopenlayers_ui.admin.js. There is an ajax request trying to perform the version_check. The call always results in error. Perhaps there is something wrong with the setting of the basePath. Now I remember I did see a lot of ajax http request terminated abnormally error pop-ups before I the OL page officially declares failure.

biydng’s picture

Status: Active » Closed (duplicate)

Closed. Changed to the newly created issue: OpenLayers UI admin version check ajax error.

LauriLarjo’s picture

Category: support » bug
Priority: Critical » Normal
Status: Closed (duplicate) » Active
StatusFileSize
new78.59 KB

This happens to me now. It doesn't have to do with ajax javascript, but to me it seems that openlayers.module has a bug.
I debugged the problem to rise from openlayers.module function openlayers_layer_load().
This call
$layer = ctools_export_load_object('openlayers_layers', 'names', array($name));
returns empty array as $layer.

I don't know why, but this function call is done everytime I'm loading a page starting with /admin/structure/openlayers/layers.
So page load at /admin/structure/openlayers/layers/add causes watchdog error: "Layer add not found."
Page load at /admin/structure/openlayers/layers causes watchdog error "Layer not found."
Page load at /admin/structure/openlayers/layers/test_layer causes watchdog error "Layer test_layer not found" (as it should, since I don't have such a layer)

I do have a layer called "locations_openlayers_1", so page load at /admin/structure/openlayers/layers/locations_openlayers_1 does not cause errors.

zzolo’s picture

Status: Active » Fixed

This has been fixed in dev.

Status: Fixed » Closed (fixed)

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

llorberb’s picture

Dev version is working for me. It was a little bit different issue - layer not found only came up as an error when I was saving a Map.

Also @zzolo - your book has been a huge help. Thanks.

riskogab’s picture

I had the same problem ("Error making request to server.") and solved if in .htaccess uncomment the line wich contains RewriteBase /.

JSCSJSCS’s picture

I downloaded and installed the 7.x-3.x-dev version and got he same "Layer not found" reports log entry. After reading this issue, I uninstalled that version and DL and installed the 7.x-2.x-dev version and I did not get that log entry error message. I was surprised how different the two settings pages were, especially with regard to the libraries.