Hi

Under admin/settings/gmaps I see

Enabled countries:
If none selected all countries will be included.

Is it supposed to list the countries here by any chance - if yes then I dont see them

Also I have not managed to find out a way to link my nodes to gmaps

Comments

xmarket’s picture

xmarket commented

That list is populated by the content of your site, so it must be empty before the submit of the first "gmaps content".

manuj_78’s picture

manuj_78 commented

Hi xmarket,
can you elaborate a bit on the installation instructions please as I cant seem to figure out a way to associate node types to gmaps.in gcg it was just a matter of selecting a checkbox for node types but I dont think that is the case here

Manuj

xmarket’s picture

xmarket commented

I updated the project page, please take a look to it..... especially to the mini HOWTOs...

manuj_78’s picture

manuj_78 commented
Category: bug » feature

Changing this to feature request
From reading the instructions on the project homepage, it seems that to associate gmaps with standard node types like page etc we need to add fields to the node types which from my understanding will basically change these node types to cck type nodes.
Can I request the ability to have this functionality without adding the fields also - ie a similar functionality to gcg for associating maps to node types

2) Is it possible to make the vocabularies visible under categories list. I have an existing taxonomy list with names of regions etc which I would like to merge into the terms that this module will create.

xmarket’s picture

xmarket commented

1) Most of the cck functionality will be moved to the D7 core, which means, this will be the standard way to extend nodes. Otherwise CCK doesn't change any node types into "cck node types". CCK is just a generic API to add fields (like title and body) to nodes.

2) Because of perfomance an usability reasons andresses must be stored in their own storage (db table). This is a must. If you would like to integrate addresses whith taxonomy you should store them as adresses and as terms, too, and you should synchronize the two storage. But sync requires that you should disable all modification capabilities of the generated terms, whick makes the entire integration meaningless. I think the right way to solve your proble is to extend the location taxonomy to accept taxonomy term arguments, which will allow you to mix your custom address vocabularies with autogenerated ones.

xmarket’s picture

xmarket commented
Status: Active » Closed (fixed)