DB error when adding nodes with multiple marker-enabled tags

Same problem happens to me, any idea how to solve this?

same issue for me - have a taxonomy on a node that enables multiple selection as above

I'm experiencing this problem. My solution was to only add markers for 1st level terms, not 2nd level terms (I had to go into the database and delete the unwanted ones manually). I know that this assumes that the taxonomy has a hierarchy and only some terms having a marker type.

If you want multiple tags for multiple markers, what decides which markers to display? AFter all, there's only one marker on the map per location.

I think the middle-road is for the code to select the taxonomy term with the 'lightest weight', assuming that taxonomy terms have weights in the first place. Another option (if you have a hierarchy) is that you only add the markers for taxonomy terms that have no parent.

forgot to put in my deets:
gmap 7.x-2.8
location 7.x-3.0-rc6

why the errors are ignored for years?

also interested in a fix for this.

here is quick patch that solves the issue: add a break in line 209 of gmap_taxonomy.module file

      // Insert to gmap_taxonomy table
      db_insert('gmap_taxonomy_node')
        ->fields(array(
          'nid' => $node->nid,
          'tid' => $term['tid'],
          'marker' => $gmap_taxonomy_markers[$term['tid']],
        ))
        ->execute();

      // @20150324 by cossme
      // because only 1 term marker per node is allowed (db schema constraint) break here
      // @see https://www.drupal.org/node/2043673
      break;
    }
}

[edit] sorry, I was to fast: in order to get this to work you also need to drop the column "vid" in gmap_taxonomy_node - that column and the fact that it was removed from the schema without actually dropping it from the table is the true cause of the error. [/edit]

Patch #6 works great for me!

-- unwanted double posting TO BE REMOVED --

I can confirm the patch works and is logically okay. Please remove the unnecessary comments from the patch when applying it against the dev release.

This should be fixed ASAP, because the problem leads to a database error. Thanks a lot for your good work. Setting this RTBC.

If we want to fix this problem, we have to add delta field to the mysql table.
@podarok - can I do this here?

@anpolimus this sounds like feature request, not a bug report

The issue is still open and leads to errors... please help! It's RTBC!

Patch can't be applied. Needs reroll

Reroll

Reroll 2

Sorry. Here's the hopefully final one that works.

#19 is RTBC.
@Module maintainer: Please apply and add to the next stable release. This bug is really disturbing.

#19 is merged
Thanks

added upport issue https://github.com/drupal-ukraine/dmaps/issues/77

I would like to reopen this issue - because I use the current gmap version 7.x-2.11 with has included the patch mentioned here in this threat.

but if I edit an existing node and klick on save, I get the same error message :-(
I have only one marker related to on taxonomy term and only one taxonomy entry related to a node. ok, there are several vocabulary connected to the content type but only one taxonomy is relevant for the marker type.

my site is a migrated D6 site - the D6 site works without problems.
I use GMAP and LOCATION modules to store geodata to Node Locations in D7 because of migration from D6.

I have several problems to make the migration work under D7 (unfortunately not D8 because of missing a lot of Modules in D8, especially GMAP and LOCATION :-( )

I need urgent help on this issue - anybody an idea?