On Mar 16, 9:40 am, "[email protected]" <[email protected]> wrote: > Accessing the file directly works - I've already entered the MIME > information for IIS. IE, FF, Chrome and Safari have access to it. > > I'm using the enterprise API
Try your enterprise representative. I'm not sure we are going to be able to help as we can't see your KML files or your maps. If you can put them somewhere public and replicate the problem, then someone might have some insight. > , KML Validates perfectly. This just > recently happened. > No updates to our site at all, and one day bam it stopped working. I'm always suspicious when someone says this. I have rarely found it to be true. If it is true, does reverting the API version to an earlier version help? v1.40 would be one candidate to try if it stopped working in the last couple of weeks. -- Larry > > On Mar 13, 6:06 pm, Rossko <[email protected]> wrote: > > > > > > this is a KML file that is now erroring: > > > So actually it's not your KML file at all, and of no value at all. > > > What happens if you access a file directly in a browser? (as we're not > > allowed to try) > > Try both IE and FF as they behave differently. > > > What happens if you open your KML in the Google Maps page, rather than > > the API? > > Are you even using the API? Which KML parser are you using? > > > What happens if you use one of the KML validation services on your > > files? > > >http://groups.google.com/group/Google-Maps-API/web/suggested-posting-... > > > cheers, Ross K- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
