Which browser does this happen in?
I just checked it, and it does work fine for me. But I do know that sometimes browsers autocomplete input fields and show old info, which in this case would be the latlng and that would result in the marker ending up in the wrong location.
But to be sure you would have to check the wpsl_stores table in the db. If you open it, and write down the current latlng for a location. Then drag the marker to a different location and update it. Then check if the latlng fields have changed in the db or are still the same.
I found the problem, someone else reported it as well and I had a closer look at the code. It doesn’t happen all the time, but it should never happen in the first place.
If you open the js/wpsl-gmap.js file and look for this line, it is inside the ‘function addMarker’
google.maps.event.addListener( marker, "dragend", function() {
geocodeDraggedPosition( marker.getPosition() );
});
Replace it with this.
google.maps.event.addListener( marker, "dragend", function() {
setLatlng( marker.getPosition(), "store" );
});
I will include this in the 2.0 update, but I’m still writing the documentation and polishing the code before will release it.
It is in the /admin/js/wpsl-admin.js file instead of js/wpsl-gmap.js 🙂
