Search in the group for your question/error first(e.g. "removing markers" or "error: a has no properties") - you're likely to find threads with relevant answers. Many issues/questions are common and have been answered before.
Also, check out the documentation, frequently asked questions, and terms of use.
However, please don't add your query to an existing discussion thread unless you are absolutely certain that it's the same issue. It's better to start a new thread.
If you're in the right group and still haven't found the answer to your question in the resources, read these posting guidelines to make sure that you'll get a helpful response:
Post a link to your map online. Pasting a handful of lines of your code is fine to highlight a small section you've got questions about, but most developers here will not debug your problem or comment on your question unless you provide a URL to the map online. More on this important point at the bottom of the page. If you have no server yet, or if you're worried about uploading unfinished code to your company's server, upload to Tripod, Geocities, or other free hosts.
Don't post any code from the API itself, and please don't post a code snippet unless you are absolutely certain that it's the part you need to ask about. In a sizeable proportion of cases, it's not the code which is at fault, it's the data, and this can only be checked with a link so that others can experience what you do. Don't post error messages without posting a link to your map. API error messages tend not to be informative.
Describe theOperating System and Browser versions that you experience the error in (e.g. Mac OS/X, Safari; Win XP SP3, IE7). Please don't forget to describe exactly how to reproduce the problem you experience. Include any data needed -- you may know your postcode/zipcode system (for example), but others probably won't. If you get an error message, quote the exact message (copy/paste if possible).
Note: If you haven't posted before, your post will need to be moderated before it appears. Generally this happens quite quickly, but it could take as long as 12 hours. Please wait before repeating your posting. Moderation of new members is an anti-spam measure, and should only affect your first post to the group.
If you're new to Javascript programming or Object-oriented programming concepts, consider going through some of the many available tutorials on the web first, so that you can understand the advice given to you here. If you don't want to learn programming but want a simple map on your site, consider creating an embeddable Google My Map instead.
If you're new to debugging JavaScript, consider using Firefox's Error Console (under Tools menu), or for more extensive debugging, download the Firebug plug-in for Firefox. If you don't understand the meaning of the error in the console, report it in your post. For an intro to those tools, watch this screencast.
Try running your page/code though validators, they can often spot errors even quicker than fellow developers! Examples include - JSLint jslint.com - W3C validator validator.w3.org - and feedvalidator.org (good for KML).
As one of our top contributors so eloquently put it, the reasons why we always suggest posting a link are simple:
90% of the time the error is outside of what is posted.
Posting code usually garbles the actual code, which makes it impossible to debug. A simple thing like a missing semicolon on a line will cause code to fail.
It is impossible to use the standard tools of debuggers, like Firebug without running it through an actual site.
The rules of the game (Google's TOU) state that "The API may be used only for services that are generally accessible to consumers without charge." and as such, a link proves that you're playing along nicely.
A lot of posted code contains things like "mysite.com" links to xml files, etc. There is no point in being secretive. If you want to be secretive, don't ask for free advice.
Most of us don't like reading posted code. It's a waste of time and we have better things to do. If you want free help from an expert, I suggest making it easy for those people to help you.
We hope this clears up the reason why we ask for links. It constitutes the "rules of engagement" for asking advice.
Updated the layout to break up the text a bit, also make some points
more prominent. No substantial content change. Just want to make sure
the important points aren't missed ;)
Click on http://groups.google.com/group/Google-Maps-API/web/suggested-posting-guidelines
- or copy & paste it into your browser's address bar if that doesn't
Sep 8 2008 by Esa
There are some wonderful recources that should be advertised in the
first paragraph.
- JSLint http://www.jslint.com/
- W3C validator http://validator.w3.org/check
A bookmarklet that sends the page to validator might be there but I
don't know how to put a bookmarklet on Groups
<a href="javascript:document.location.href = 'http://validator.w3.org/
Sep 7 2008 by pamela (Google Employee)
I know its a fine line between learning more javascript and learning javascript. There are two concepts that we teach here that you actually don't often learn from just knowing Javascript as a programming language - asynchronous callbacks and function closures. Those of the kind of concepts that are fine to be taught here, as
