IE message:"Error during map rendering: TypeError: Unable to get value of the property 'transform': object is null or undefined"

Similar has been reportetd here: http://drupal.org/node/1364304#comment-7085944

I get the error-message in IE8: Error during map rendering: TypeError: 'geometry' is null or not an object

If I disable all the layers from views the map works fine in IE8.

I know on one of the recent dev updates, there was a modification to the projections. I had to go back and update all of my layers to EPSG: 900913 instead of 900913. After making the change it worked in IE8 fine. Not sure if that is the case on the beta version but worth checking.

Diana,

You should take time to read a bit and stop spamming the issue queue.
Reporting a problem doesn't mean that you will have it fixed within the day or the week.
I'm doing my best to fix all the problems and you don't help.

I'm working on the 2.x so, it's better for you to use the 7.x-2.x-dev tar.gz (186.07 KB) | zip (277.36 KB) 2013-Feb-18 Notes.

Thanks for understanding.

Hi Pol, I wasnt spamming the issue queue.

Yes you are.

yes that was me who posted it in the other place. Since no one has responded at all I was hoping to get more attention by posting it in two places. Does anyone have any idea of where I should start looking to try to debug this?

You see, this is spamming.

My boss wants me to get this fixed and I had no idea you had read or were working on this problem at all. If you had told me you were working on it I would be more patient.

Yes, patience is the key. That doesn't mean that it will be fixed within hours or days. Deal with it.
I suggest you to tell your boss that it might take a bit more time.

I'm sure I'm not the only one who feels there has to be more communication and explanation. for instance to have two dev versions with dates that dont make sense is very confusing and it would be best if it's explained.

It's explained. Just read.

Thanks and I hope we keep communicating more often.

And I hope to have more help and more constructive people. That kind of post are useless and makes me loses my precious time.

I work on a lot of stuff and when I have time, I work for free, for you, this is Open Source.
If something is not done, then do it yourself, share it with the community and we'll improve it together.

I really enjoy what I do and I work on what I think should be done first.

I don't work with Microsoft browsers, so I can't help you, you have to find a solution by yourself, for example, by editing the file openlayers.js and understand how it works, so you'll understand why it fails in IE and you'll probably find a workaround.

Diana,

I'm not angry at you at all, I'm just explaining to you how Open Source works.

The key is in the word itself 'Source' and 'just read', it means that if you read the source, you'll understand.
Reading the source is the first things to do when you have a bug, I shouldn't repeat that, it's self explanatory, it's the best hint that everyone knows.

Anyway, I hope you'll find a solution.

Diana,

OpenLayers 2.12 is now the default library, it has been enabled by default in the latest changelog: http://drupal.org/node/1876564

I'm glad that you'll help us, it's greatly appreciated.

I just did a new drupal installation with a minimum module set enabled:

• views
• geocoder
• addressfield
• geofield
• and the other depending modules

And everything works just fine in IE8 (an the other browsers)
Will now try to narrow down the the conflicting module.

update: So far I can tell that AIS (http://drupal.org/project/ais) breaks the IE 8 functionality of this module.

Maps work fine in IE9 and modern browsers, however get an empty map on IE8/7.

Hello,

I have committed the patch #16 from amdk8.

Feedback is welcome.

Thanks.

I know on one of the recent dev updates, there was a modification to the projections. I had to go back and update all of my layers to EPSG: 900913 instead of 900913. […]

Please report such problems in the related issue #1331410 because they can only be fixed when they are known. As of today this change is applied on update automatically.

More general notes:

• Do always provide a stack trace along with your reports as this allows for more efficient problem resolution.
• As Pol said, this is an open source project so the priorities of the developers are not necessarily yours.
  • IE is only the most used browser in some markets/areas. There are many scenarios where one simply does not care about IE support (for example some intranets and spare-time projects). If you are a Microsoft customer and it turns out your problem is caused by their bug, report the issue to them.
  • If you feel your issue gets ignored, state clearly what you need and in case of bugs how to reproduce.
  • Consider offering to pay for a solution. Maybe somebody offers his time then (perhaps somebody who never worked on the project before).