SL Google Map Field Type : Google Maps in your CP, SAEFs, and EE templates : Now with map types in the CP

Thinking about it, it would be useful to also specify that a weblog entry has no location. At the moment, it saves the default location.

That’s a good point, and not something I’ve come across before.

I’ll look into implementing it, and putting out a bug fix release.

Cheers, Stephen

Thanks Stephen. It’s a very useful plugin btw. Showed it to a client today and they were just amazed I could add that as a feature in literally 15 minutes after they’d said yes.

Hi everyone, I’ve had a skim read over this thread and saw a couple of mentions of multiple pins on one map but didn’t see any definitive answer. So my question is are multiple pins going to be supported on a single map any time soon or is that likely to be a V2 feature?

Finally just wanted to say a big thank you Stephen, without people like you building awesome addons EE wouldn’t be what it is today.

So my question is are multiple pins going to be supported on a single map any time soon or is that likely to be a V2 feature?

A version 2 feature, definitely.

Finally just wanted to say a big thank you Stephen, without people like you building awesome addons EE wouldn’t be what it is today.

Thanks Ben, I really appreciate it.

Cheers, Stephen

Thanks so much for this Stephen - I’m using it in a SAEF and it works great. One question though: can you (or anyone else?) tell me if it’s possible to change - or maybe even remove - the “search” text below the map that reads “Enter an address (e.g. Oxford Street, London) or a postal code”?

Nevermind - I can of course do this in the language file. Need sleep.

I’m using this in a SAEF … is there a way to conceal the location of my system directory in this case? Unlike standard template usage, the js appears to be included automatically.

I’m using this in a SAEF … is there a way to conceal the location of my system directory in this case?

Not currently, no. The same code is used to render the field in both the Publish / Edit form, and a SAEF (which is standard practise for a FieldFrame fieldtype), hence the automatic inclusion of the required JavaScript files.

Cheers, Stephen

Thanks Stephen …. for your reply and for creating this extension. Thought you might be interested in this related discussion:

http://ellislab.com/forums/viewthread/144383/

Thought you might be interested in this related discussion

Thanks, Ingmar makes some good points. I’ll bear them in mind for any future releases.

Cheers, Stephen

Stephen,

I’m getting some weird behavior from this add-on. The map is being cut with a very small vertical height. I’m not sure if is is from the extension/field type itself or whether this is a product of my code or development environment, which in this case, is a local server running under XAMPP 1.7.3 and Windows 7 x64.

The API Key was registered with the domain being my http://localhost/impakt/.

Here’s my code:

{exp:weblog:entries weblog="static" limit="1"}

    <h2>{title}</h2>

    {loc-map controls="zoom" map="click_zoom|scroll_zoom" pin="drag|center"}
        {map}This is the fallback content for users who cannot see the Google Map.{/map}
    {/loc-map}

{/exp:weblog:entries}

To my knowledge, I’m running the latest version of everything:

• FieldFrame 1.3.5
• SL Google Maps 1.1.2
• ExpressionEngine 1.6.8 Build 20100121

Tested in Firefox 3.6, Chrome 4.0.295.0, Opera 10.5, and IE 8.

I got that too when I first started using the extension and just had to create some css to set the height of the element for me. That fixed it right up.

Best wishes,

Mark

I got that too when I first started using the extension and just had to create some css to set the height of the element for me. That fixed it right up. Best wishes, Mark

Mark,

Thanks for pointing that out to me. I was throwing the content structure before templating, so it’s relatively barebones in its current state. A big kudos for the small, but what should’ve been obvious to me tip. Sometimes it’s the little things that count! =)

Cheers!

Mark, Thanks for pointing that out to me. I was throwing the content structure before templating, so it’s relatively barebones in its current state. A big kudos for the small, but what should’ve been obvious to me tip. Sometimes it’s the little things that count! =) Cheers!

No problem at all. I had the exact same thought when I first used it and thought that it should look the same as it did in the control panel.

Glad it’s all sorted for you now though.

Best wishes,

Mark