You can place the {mosmap} inside the content of article. Doesn't need to be in the html of the content.

Check the following parts:

  • Check at the parameters of the plugin if the parameter published (on right side) is Yes.
    This parameter is default 'No'. The parameter is necessary so we can remove the {mosmap}  code if you want the plugin to be unpublished.
  • The preview in the backend won't show the map, because the plugin isn't called. You will see the code {mosmap} in the preview.
  • Check the html of the content item so there are no < br> or & nbsp; between { } or in the html a return.
    If you work with pure html code, be sure that there isn't any " \r\n " tags  in the mosmap string between { } in your database code.
    Place it at the start of a line. The plugin works for one line!
  • In the text parameter don't use (double) quotes in html-tags.
  • The plugin doesn't work correctly with the WYSIWYG editor JCE, because JCE doesn't place the code in one line and translates quotes and other special characters.
    For JCE have a look into your setup-Section under Joomla-Admin-Backend Components]-[JCE-Admin]-[JCE-Configuration] in Section [Entity Encoding]. There are the possible options [Numeric], [Named], [RAW]. Try the option and see what's working bet for the plugin.
    But pay Attention: If you work with other Authors or Publisher, you maybe in trouble with some of Features, or Plugins by JCE.
  • Validate your page to see if it's valid html (see:
  • Place in your template all <meta> entities directly behind the <head> together.
  • Also check the css-file of your template and if it exists remove the following:

    div {

  • For responsive template, you must set the widht to 100%, the height to an absolute number like 400px and make sure that the {mosmap} command is plaved in a responsive div that resizes when the window is resized.
  • If you get a message the the Google API key isn't valid, check the URL of the websiteby by entering: "javascript:alert('http://'" in the addressfield of your browser.Check if this is the same as registred or as referer defined.
  • If you have special characters in your IDN-domain then the key for google maps will not work allright. See Issue 12 of GMaps API.
    For example: www.østerhø won't work.
  • If a infowindow doesn't capture all content with an image: you need to set the width and height of the image inside the html code instead of nothing. The first time the browser doesn't know the size of the image and will load a standard infowindow. Second time the image is in the cache and the browser knows the size of the image and the infowindow is allright.
  • There can be a conflict between javascript frameworks like prototype, Mootools and jQuery. Mootools is default delivered by Joomla 1.5/1.6.
    To solve conflicts with jQuery add this to your template below jQuery.js (see:

    // Use jQuery via jQuery(...)
    // Use Prototype/Mootools with $(...), etc.

    Or have a look at this article.
    Or set the plugin the parameter "Load with mootools?" to timeinterval. Then the map may show.
  • When other modules give javascript errors then the map may not show. You can try to set in the configuration of the plugin the parameter "Load with mootools?" to timeinterval. Then the map may show.
    Of course best solution is to solve the javascript errors.
  • If you place a link inside the infowindow then it will always open in a new window or tab!
    You can use a kml-file and GeoXML to open a link in the same window (see kml sidebar).
  • If you use Simple Image Gallery (SIG) then there can be conflict. The free SIG version loads its javascripts everytime without checking if the already exists and breaks the already loaded javascripts. With the SIG pro you can solve the problem by choosing mootools.
    You can try to load SIG plugin before Google Maps Plugin so change the order in the plugin manager.
  • If using the compressor plugin with your google map plugin, the admin should configure the compressor plugin to exclude javascript of the googlemaps plugin because they already are compressed. Currenlty the kml renderer's javascript file (ex: geoxml.js) will not work when compressed twice. The plugin's parameters provide a place where you can exclude a list of specific CSS and JS files.  Just simply enter 'geoxml.js' into one of the excluded JS file fields, and it will work properly.
  • There are extensions for browsers that checks the generated html page, the related images and the css/javascript file and filter out specific code so advertisements are not shows or other suspieus stuff. For example BFilter available on the Mac will give a remark that the google maps api scripts(<script src=";v=2.x&amp;oe=utf-8&amp;hl=en&amp;key=....&sensor=false&indexing=true" type="text/javascript"></script>) has too many unrelated nested scripts.
    So the maps will not work.
  • If the Earth maptype gives an error that the key is not vaild, check the generated source of the page if there are extensions that load a google script without a key. For example:
    <script src="" type="text/javascript"></script>

    Disable this extension or add your key also in this extension.

  • If you get an error on the frontpage: Fatal error: Call to undefined function mb_check_encoding().
    Check if the php library PHP Multibyte Stringsisinstalled, see: Ask yourhosting provider to install this library.
  • If you activate the SEO urls in Joomla then you need to check the urls of all your images and urls in the mosmap command. You need to be sure that you have a / before the url, so for example /images/icon_name.png.

You can use Firefox with Firebug to inspect the styling on the specific object on the page to see what styling interferes with the corners.

Or you must debug your template by:

  1. Save the source of your page (generated by joomla) as a html page
  2. Now you can edit it and open it in a browser.
  3. Maybe you need to add a <base href="/" /> when design is not allright or javascript and image are not found.
  4. Step by step remove javascript to see if problem disappear.
  5. If you found the right javascript check if you really need it otherwise try to solve the problem.
  6. If not found the problem remove the one by one the link to css files.
  7. If you found the right css-file then you have to debug this and remove one by one the defined styles to see if the problem disappear.