Clicking just to the side of a point sends you to a broken link page. This also occasionally happens clicking on the point itself.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | OpenLayers.js_.zip | 193.05 KB | tmcw |
| #2 | mid_firefox_error.png | 9.11 KB | jmcl |
| #2 | mid_firefox.png | 176.15 KB | jmcl |
Comments
Comment #1
tmcw commentedWhat page in particular does it bring you to? Is there an online example of this bug?
Comment #2
jmcl commentedAt the moment the site is in development behind a firewall. However, I have attached images that hopefully will explain better what is going on.
Comment #3
tmcw commentedWhat click behavior is enabled here? Or which behaviors in general?
Comment #4
jmcl commentedI disabled WFS and the error stopped occuring, so the error is with WFS not Openlayers.
Comment #5
tmcw commentedMoving to the WFS module, then.
Comment #6
tmcw commentedThis problem is very, very likely derived from this upstream bug in the OpenLayers javascript library. It can be averted by applying the patch there or using a patched version of OpenLayers.js, as attached.
Comment #7
tmcw commentedWell, this is an upstream bug in OpenLayers, and there's nothing that I can do to fix it beyond futher supporting the patch I've submitted to ol.org.
Comment #8
azuledu commentedSame error for me. I always get "/undefined" url.
I'm using the patched version of openlayers.js
I don't understand the line "url = $(url).attr('href');" in wfs_behavior_virtualclick.js file. This is the line which sets url=undefined.
Any idea?
Thanks.
Comment #9
tmcw commentedThat line is trying to get the URL out of a linked field - basically it takes the element and gets the 'href' attribute, which is the URL. The most likely cause of this problem is that you're using a stock OpenLayers instead of the one linked above - the stock version is unable to get HTML from the WFS protocol.