Hello,
There is no map after update to 5.8. Only 'Javascript is required to view this map.'..., as seen in other thread.
Looking in memory for any previous patches, but don't remember any...
Any help, guys? :]
Szy.
Hello,
There is no map after update to 5.8. Only 'Javascript is required to view this map.'..., as seen in other thread.
Looking in memory for any previous patches, but don't remember any...
Any help, guys? :]
Szy.
Comments
Comment #1
szy commentedComment #2
rokrI second that.
The block 'Location map' doesn't work anymore.
Another Block with custom code to show a map also stopped working.
I just see a blank div with nothing else in it.
Maps like node locations and user locations still work.
I'm using a dev version from early 2008.
At pages like "node locations" and "user locations" all gmap *.js files are injected.
At nodes with only a gmap block no *.js are injected at the beginning of the resulting html.
The interesting thing: also DHTML menu stopped working after upgraded to d5.8 showing the same *.js behaviour.
#281049: After upgrade to Drupal 5.8, DHTML Menu no longer works
Update: looks like a bug in block.module:
#281026: block module from 5.8 breaks css and js (reverting to 5.7 block.module fixes problem)
Comment #3
Mark Linden commentedsubscribing
Comment #4
JimBroad commentedI have a custom block in a module that renders a google map that also quit with 5.8 upgrade.
I seem to have tracked it down to block.module
then found this:
http://drupal.org/node/232037#comment-916605
probably same issue you guys are having with GMap
Comment #5
Mark Linden commentedanyone see a difference with 5.9 ?
Comment #6
rokrThis has been fixed by drupal core 5.9 and works for me. The issue is adressed here:
#281042: regression in 5.8 from 5.7 theme('blocks','all') broken - so no header alteration possible
So this specific gmap issue can be closed.
Ronald
Comment #7
soupp commentedDouble that. Upgrading 5.8 -> 5.9 did help to solve this issue for me. GMap module is Beta 3 though.
Comment #8
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.