Hello, I've noticed a (JavaScript) bug in the current dev (09/14/2010) and beta3 versions. This bug occurs on the node/edit and node/add form. The bug only occurs when Google, Yahoo and Microsoft have been set as default providers in the module administration page.

The error messages according to firebug:

  • GMap2 is not defined (line 286 in idelabmapstraction.js)
  • YMap is not defined (line 362 in idelabmapstraction.js)
  • VEMap is not defined (line 340 in idelabmapstraction.js)

This might be problem cause IDELab's Mapstraction or by this module, I am not sure about that.

Comments

plopesc’s picture

plopesc
he/him
Primary language Spanish
commented

Hello,

I don't understand your issue, because only can be one default provider, and you talk about three different default providers.

Please, explain better your problem and how can I reproduce it.

Thanks for your interest in the module.

plopesc

KhaledBlah’s picture

KhaledBlah commented

Hi plopesc,

what I'm trying to say that the the error "GMap2 is not defined" occurs when Google has been set as the default provider and the error "YMap..." when Yahoo and so on. You can reproduce the error when adding a node that has a Mapstraction CCK map field. In case you use Firefox and have firebug installed, it should then present you with an error depending on what default provider you've set.

Regards,
Khaled

plopesc’s picture

plopesc
he/him
Primary language Spanish
commented

Hello,

I can't reproduce your error, I tried to create nodes in my local environment and in the test page (http://cmsmap.idelab.uva.es) and the error is not shown.

Moreover, the default provider property only is used to the map formatters rarely. It should not be used in the node/add or node/edit pages.

Beta 3 version includes some changes in the module core, if you upgrade the module form beta2 version, you can try to uninstall and reinstall the module. If it doesn't work, I will need more info to try to help you.

Best Regards,

plopesc

KhaledBlah’s picture

KhaledBlah commented

Hello,

sorry for my late reply. I am happy to give you more information. The problem still occurs for me. I've tried it with both Firefox 3.6 and Google Chrome on Ubuntu 10.04. I have deleted my geo field and re-installed the module (beta3) and then created a new geo field and still get the same result.

What kind of information do you need from me?

Regards,
Khaled

plopesc’s picture

plopesc
he/him
Primary language Spanish
commented

Hello,

I am very confused about your problem. I don't know how to reproduce it, and the cause is a mistery for me...

Previous module releases worked OK in your site?

Are there any view or Mapstraction CCK block in the node/add or node/edit page in your site?

Sorry to be so lost, but can not find a way to solve the problem.

Regards,
plopesc

KhaledBlah’s picture

KhaledBlah commented

Hello,

I have done some more test and the module does work correctly when the JavaScript files are referenced from IDELab's website. However, if I download the IDELab release and put it into my sites/all/modules/libraries folders it will not work. Can you confirm this?

Regards,
Khaled

plopesc’s picture

plopesc
he/him
Primary language Spanish
commented

Hello,

From where you downloaded the library script?

I think that it doesn't matter, because in my own site, the script is included in a local folder.

Be sure that the script is called idelabmapstraction.js and you don't include that name in the path field.

If the problem is in the script, you can copy the content of http://mvn.idelab.uva.es/idelabmapstraction/downloads/idelabmapstraction.js in a new file called idelabmapstraction.js and store it in your local folder.

Regards,
plopesc

KhaledBlah’s picture

KhaledBlah commented

Hello,

the path I used was: sites/all/libraries/mapstraction_cck/idelabmapstraction-1.1-release which I now changed to sites/all/libraries/mapstraction_cck/javascript. Now it seems to be working fine. However, I could not find a warning that the script name may not be part of the path so you'll maybe want to add this to the description for the local path.

Thanks and regards,
Khaled

plopesc’s picture

plopesc
he/him
Primary language Spanish
commented
Status: Active » Closed (fixed)

OK

Thanks for your collaboration. I will include in a more visible way that requirement. Now it is only included in the description of the path field.

Regards,
plopesc