This plugin hasn’t been tested with the latest 3 major releases of WordPress. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.

Current Location


The plugin uses the Google Badge System and pulls the JSON file. The plugin then parses through the json file and displays your current location. You need to have a Google Account and signed into Google Latitude on your computer/mobile device. The idea behind this plugin is have my blog display my current location without my editing anything.

This plugin requires php5 or greater.


  1. Copy the folder ‘current-location’ into the directory ‘wp-content/plugins/’.

  2. Activate the plugin.

  3. Find the Current Location settings button in your side of the ‘wp-admin’ panel.

  4. Update all settings.

  5. Add ‘<?php echo display_current_location(); ?>’ to your template. OR Add [current-location] to your posts. OR Add the Current Location Widget.


If your question isn’t here, ask your own question at the forums.

Output says this «User ID incorrect. You entered this id: Nothing»

You need to visit the Current Location settings page and update the Google Badge UserID.

On the settings page you see this note: «Since you are using an older version of WordPress, the timestamp output will be set to the server.»

All that means is your not using WordPress 2.8, which is fine, but the new TimeZone feature in 2.8 will fix the timestamp to your local blog timezone instead of your server timezone. Example: My server is located in the EST timezone but I want my blog on the CST. This will fix the timestamps for CST not EST.


There are no reviews for this plugin.

Contributors & Developers

“Current Location” is open source software. The following people have contributed to this plugin.


Translate “Current Location” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.



  • Added a Dashboard Widget so you can see what your current location is when you login.


  • Re-styled the Admin Page.


  • Updated the Post/Page Meta Information to be able to keep previously stored information. So if you edit a post, it doesn’t automatically update your Current Location. It gives you an option to update it.
  • Fixed Bug on the Page Meta Information.


  • Updated all i18n Calls with the domain in the gettext calls. I missed this early. Sorry.


  • Fixed some i18n issues.
  • Added the TinyMCE button to the Post/Page Screen.
  • Fixed a bug with the Post/Pages Meta Tags.
  • Ready for i18n!


  • Minor updates. Renamed some variables that might be used by other people.
  • Updated all the stored and echos variables to be ready for I18n.


  • Removed the userid from the error message so someone wouldn’t steal it from the output.
  • Changed the Map Zoom to Numbers instead of words.
  • Updated the Config page to show the correct usage for a template add.
  • Also fixed a bug with the Static Maps (Thanks mnbvcx)


  • Post or Pages wouldn’t display any content if you used the words current-location. Now I make sure to look for ‘[current-location’ first then try and switch it with the post meta information.


  • Minor change with display of the post/page meta data.


  • Added Widget Support.
  • Added [current-location] shortcode to the post page.
  • Added Post Meta Data to work with the [current-location] shortcode.
  • Added Static Maps as an option.


  • Didn’t release because I made major updates to the plugin so I went to 1.5 before releasing this.
  • Works with WP 2.9.2
  • Added new function to store your current location in the meta table. You need to choose to store your location on the post and it will append it to the end of the article.
  • Works with both pages and post.
  • Currently adds ‘<p>Posted from: Nashville, TN, USA</p>’ to the end of each post that has the meta data stored.


  • Fixed spelling mistakes and updating all the correct files this times 🙂
  • Updated readme, index and screenshots.


  • Still learning Subversion and upload to early. Sorry about this.


  • Removed all old comments that had my default information stored.


  • Initial upload.