Recently while debugging a site that was practically identical to another, I came across a bug introduced by Autocomplete Element which uses a different autocomplete plugin from core that is more configurable. I didn't need it, so I disabled it and my geocoder is working again. I haven't looked deeply, but my inkling is that this is javascript problem. Basically, the processor is not getting called when autocomplete element is on. Is there a place in the openlayers javascript that uses a callback tied to the core autocomplete?

Willing to investigate, but not sure if I can fix it anytime soon.

Comments

steinmb’s picture

steinmb commented

Hi :)
I'm hoping we could new alpha rolled, but issues like this need to be sorted out. Any chance for you to show us a diff/patch of what you did?

steinmb’s picture

steinmb commented
Status: Active » Postponed (maintainer needs more info)

Tested but unable to reproduce. Tested by adding a node_ref field to a content type. Both of the autocomplete widgets worked as expected. Also tried to move the field order around.

steinmb’s picture

steinmb commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)
steinmb’s picture

steinmb commented
Status: Closed (cannot reproduce) » Postponed (maintainer needs more info)

Hmm, let's keep this open....

steinmb’s picture

steinmb commented
Priority: Normal » Minor
Status: Postponed (maintainer needs more info) » Active

Managed to reproduce the bug with http://drupal.org/project/autocomplete_element. Had a look in autocomplete_element issue q and the project seems to be kinda stale and have a small install base. It still is not using jquery UI (http://drupal.org/project/jquery_ui) that most of our D6 sites this days are running with.

If there are a quick fix we might work on this. If someone contrib. a patch we will be more then happy to test and commit it.