When you click on Regenerate marker cache, the Gmap module builds a custom file called gmap_markers.js and places it in the /files/js directory where it has read/write permissions. It is my belief that for security reasons, the file needs to be made read-only and moved someplace where the Gmap module can find it. In earlier versions of Gmap, you had to set a field with the location of the file. I put mine in sites/all/libraries/gmap/ and it seems to find it automatically. Also if you are using one of the third-party marker managers, the instructions say to download the marker manager and place it in the thirdparty folder. I think that is code for the sites/all/libraries/ folder.
BTW, there is a huge amount of confusion between gmap_markers.js and gmap_marker.js which is part of the Gmap module.
Information is free, knowledge is acquired, but wisdom is earned.
gmap_markers.js
When you click on Regenerate marker cache, the Gmap module builds a custom file called gmap_markers.js and places it in the /files/js directory where it has read/write permissions. It is my belief that for security reasons, the file needs to be made read-only and moved someplace where the Gmap module can find it. In earlier versions of Gmap, you had to set a field with the location of the file. I put mine in sites/all/libraries/gmap/ and it seems to find it automatically. Also if you are using one of the third-party marker managers, the instructions say to download the marker manager and place it in the thirdparty folder. I think that is code for the sites/all/libraries/ folder.
BTW, there is a huge amount of confusion between gmap_markers.js and gmap_marker.js which is part of the Gmap module.
Information is free, knowledge is acquired, but wisdom is earned.