Hi Bill,

Check out this blog post for some instructions.  If I recall, the locations are just nodes that you setup however you like in Umbraco.  Then, when inserting the macro, you can provide an XPath expression that returns your location nodes  (ie $currentPage/ancestor-or-self::Home/Locations/Location [not tested]), and the property alias that stores your lat/long.

You might also want to check out uLocate, a newer package that does things a bit differently, and includes CSV Import functionality.

Hope this helps,
Tom 

Thanks Tom, I'll check all of the above. When you say "returns your location nodes", is this a page that contains the locations or is it a collection of pages that contain the location information of a single location? Is there an interface for setting up the location info?

I've checked that blog post but most of the links are long dead - the screencast etc and the PDF seemsto be well out of date.

I posted earlier that I was tasked with repairing an earlier installation that apparently worked fine until a few weeks ago. Would you have any dea how this could happen?

Bill

Yeah, it should return a collection of pages.  So if you have this structure

- Home
- - About
- - Locations
- - - Location 1
- - - Location 2

Your xpath might look something like:

$currentPage/ancestor-or-self::Home [@isDoc]/Locations [@isDoc]/Location [@isDoc]

And yes, I do have an idea why it stopped working :)  Google retired their Maps V2 API earlier in the month, which this package uses for Geocoding.  To fix, you'll need to replace the implementation with a version that uses the V3 API.  If you can wait a bit, I can try to dig this up as I recently ran into this as well.

-Tom

Thanks Tom. I'd really appreciate that.

Bill

I would definately look at uLocate for a store locator (blog post from those guys coming soon)

Hi Bill,

Sorry I haven't had a chance to look at this further.  But I can give you the binaries we updated to use the V3 API and you can see if that works.  I can give you the source too if needed.  I would have forked but its using SVN and I'm not up to speed with that :)

Backup your existing Nibble.Umb.Locator.dll and replace with the one in this zip, and add the second DLL.

Hope this helps - I'd side with Rich though in that you should look into using a more up to date soltuon like uLocate.

-Tom

Hi Tom,

Unforunately I'm getting a 403 forbidden recently on all my apps using the package.. just wondering if there was a fix? and if anything needed to be changed config wise or key wise?

Thanks,

Tom

Hey Tom,

I'm not aware of any 403 issues from this package.  Can you give some more specifics on what you're seeing?  Out of curiosity are you using the custom DLL above or just the stock package?

Hey Tom,

It's blowing up when trying to execute the web request:

namespace Nibble.Umb.Locator.GeoCoding.Services.Google

{

    using System;

    using System.Collections.Generic;

    using System.IO;

    using System.Net;

    using System.Web;

    using System.Xml;

    using System.Xml.XPath;

    public class GoogleGeoCoder : IGeoCoder

    {

        private string _accessKey;

        private XmlNamespaceManager _namespaceManager;

        public const string ServiceUrl = "http://maps.google.com/maps/geo?output=xml&q={0}&key={1}&oe=utf8";

        public GoogleGeoCoder(string accessKey)

        {

            if (string.IsNullOrEmpty(accessKey))

            {

                throw new ArgumentNullException("accessKey");

            }

            this._accessKey = accessKey;

        }

        private HttpWebRequest BuildWebRequest(string address)

        {

            HttpWebRequest request = (HttpWebRequest) WebRequest.Create(string.Format("http://maps.google.com/maps/geo?output=xml&q={0}&key={1}&oe=utf8", HttpUtility.UrlEncode(address), this._accessKey));

            request.Method = "GET";

            return request;

        }

Hi Tom,

Ah, sorry, now I know what you mean. Yeah, that's because Google deprecated the API this package was using. A potential solution is to use the DLLs I posted above instead. May also be worth looking into upgrading to the newer version Tim just finished called Seek and Destroy - it may only work with v6 though.

Hope this helps, Tom

Thanks for letting me know.. most appreciated!

is working on a reply...