drupal 6.14
gmap 6.x.1.0-rc2
(the following might or might not be relevant)
gmap taxonomy markers enabled to define differetn map points for categories within a CCK content node
Content Construction Kit (CCK) 6.x-2.6
Devel 6.x-1.18
Location 6.x-3.0
Everything was peachy until I ran cron for the first time. Then no markers and the following error messages:
# warning: parse_ini_file(sites/all/modules/gmap/markers/numbers.ini) [function.parse-ini-file]: failed to open stream: No such file or directory in /home/dogz/htdocs/sites/all/modules/gmap/gmap_markerinfo.inc on line 40.
# warning: parse_ini_file(sites/all/modules/gmap/markers/misc.ini) [function.parse-ini-file]: failed to open stream: No such file or directory in /home/dogz/htdocs/sites/all/modules/gmap/gmap_markerinfo.inc on line 40.
# warning: parse_ini_file(sites/all/modules/gmap/markers/days.ini) [function.parse-ini-file]: failed to open stream: No such file or directory in /home/dogz/htdocs/sites/all/modules/gmap/gmap_markerinfo.inc on line 40.
# warning: parse_ini_file(sites/all/modules/gmap/markers/colors.ini) [function.parse-ini-file]: failed to open stream: No such file or directory in /home/dogz/htdocs/sites/all/modules/gmap/gmap_markerinfo.inc on line 40.
# warning: parse_ini_file(sites/all/modules/gmap/markers/route.ini) [function.parse-ini-file]: failed to open stream: No such file or directory in /home/dogz/htdocs/sites/all/modules/gmap/gmap_markerinfo.inc on line 40.
# warning: parse_ini_file(sites/all/modules/gmap/markers/letters.ini) [function.parse-ini-file]: failed to open stream: No such file or directory in /home/dogz/htdocs/sites/all/modules/gmap/gmap_markerinfo.inc on line 40.
# warning: parse_ini_file(sites/all/modules/gmap/markers/numbers.ini) [function.parse-ini-file]: failed to open stream: No such file or directory in /home/dogz/htdocs/sites/all/modules/gmap/gmap_markerinfo.inc on line 229.
# warning: parse_ini_file(sites/all/modules/gmap/markers/misc.ini) [function.parse-ini-file]: failed to open stream: No such file or directory in /home/dogz/htdocs/sites/all/modules/gmap/gmap_markerinfo.inc on line 229.
# warning: parse_ini_file(sites/all/modules/gmap/markers/days.ini) [function.parse-ini-file]: failed to open stream: No such file or directory in /home/dogz/htdocs/sites/all/modules/gmap/gmap_markerinfo.inc on line 229.
# warning: parse_ini_file(sites/all/modules/gmap/markers/colors.ini) [function.parse-ini-file]: failed to open stream: No such file or directory in /home/dogz/htdocs/sites/all/modules/gmap/gmap_markerinfo.inc on line 229.
# warning: parse_ini_file(sites/all/modules/gmap/markers/route.ini) [function.parse-ini-file]: failed to open stream: No such file or directory in /home/dogz/htdocs/sites/all/modules/gmap/gmap_markerinfo.inc on line 229.
# warning: parse_ini_file(sites/all/modules/gmap/markers/letters.ini) [function.parse-ini-file]: failed to open stream: No such file or directory in /home/dogz/htdocs/sites/all/modules/gmap/gmap_markerinfo.inc on line 229.
# warning: parse_ini_file(sites/all/modules/gmap/markers/numbers.ini) [function.parse-ini-file]: failed to open stream: No such file or directory in /home/dogz/htdocs/sites/all/modules/gmap/gmap_markerinfo.inc on line 229.
I also get the popup "Request for invalid marker set small_purple!" small_purple is part of my custom marker set within sites/all/modules/gmap/markers
If I rebuild marker cache, it simply doubles the error output (e.g. you'd see the above displayed twice). In addition to trying this, I've cleared all caches (via devel module)
Since it worked fine on my dev server, so I was certain it would be a write permissions issue for the map_markers.js file in sites/default/files/js. I checked the files/js directory and it was CHMOD 777.
The only thing left I can think of is an incorrect path, since the path to drupal changed (though nothing within drupal) when I migrated, but I don't see a way to change this without hacking the path variables within gmap_markerinfo.inc.
I have seen similar support requests posted by several others, but there was never a solution posted. The issue just seemed to mysteriously vanish for some. Unfortunately for me, after two days of troubleshooting (and a lot of anguish), this is still a problem. Please help, o gmap gurus, I'm dying here!
Comments
Comment #1
baaj commentedUpdate - I hard coded the full server path within the offending lines of the module - all the errors are gone, but still nothing is getting written to the js file. WTF
Nobody wants to touch this one, eh?
Comment #2
baaj commentednobody?
Comment #3
baaj commentedFixed. I had to downgrade to gmap 1.0, then upgrade again. So, when everything else fails, reinstall....
Comment #4
baaj commentedmislabelled originally