MECTILE

Tag: XML

  • Google Map v2.1 released – now with KML support

    The release of Goole Map version 2.1 supports KML files which once displayed can even be downloaded as GPX files. Download from the WordPress plugin repository. The following example uses the included example.kml file. tgooglemap(example.kml) The following examples use the included example.xml file. Marker Z – no HTML, nonclickable. Marker 1 – standard maker with…

  • Ultimate Google Maps XML JavaScript function

    I believe I have come up with the most versatile Google Maps function. Parameters are Dev ID name (devid), XML location (xml), zoom and map type (zoom). To use it you will need to do the following; Script header: DIV in the body: XML in the following form: And the JavaScript code: Example map tgooglemap(example.xml)

  • WordPress Tool – a WordPress error and link extractor

    Here is a simple tool that might be useful to others, it does two main things; Parses your post’s content as XML and spits out any possible errors, and Extracts all external links, which can be exported as an Excel Tab delimited file. Post’s content errors Each post’s content is wrapped with XML dummy tags…

  • Google Map version 1.4.6.1

    Latest offering has cleaned up JavaScript, improved error handling, improved RoboGEO handling of XML, but main features are. Icons now support letters ‘A’ to ‘Z’. Non clickable markers if no ‘html’ element is present. In the below example Marker Z is not clickable. tgooglemap(example.xml) Download the latest from the WordPress repository.

  • tGoogleMap v1.3

    I have finally managed to get WordPress to update the version number. This problem was due to not updating the version number in the PHP file as well as the readme.txt. Version 1.3 fixes a problem with tGoogleMap not displaying correctly when a WordPress blog isn’t located in the domain folder. I have seen a…

  • GoogleMap v1.1

    tGoogleMap v1.1 has been released with major updates: cross-domain XML files can be used as the map data, see example below. due to WordPress plugin repository automatically zipping plugins, the main plugin folder is changed. Anyone upgrading from v1.0, requires deletion of old folder. Lots of code improvements, was a bug with displaying the default…