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

Here is the CSS Code:

#map
{
height: 250px;
width: 280px;
border: 1px solid black;
text-align: center;
}

And here is my actual template code:

{maplink id="map" controls="zoom|map_type" map="click_zoom|scroll_zoom" pin="center"}
{map}No map could be displayed{/map}
{/maplink}

maplink is the name of my custom field. What fixed it was this:

id="map"

note that “map” in the pair matches the id of the css div. HTH. Vee

Hey Vee. Thanks for the post. It cleared up my confusion and fixed the problem. Good stuff!

Ok, after working a bit more with this extension and using SAEF… I have run into a problem that I’m not sure how to solve.

I can get the Stand Alone Edit Form to work fine if I already have an entry in the db. However, if I don’t already have an entry in the db… nothing shows up. So I’m trying to figure out how would I use a Stand Alone Entry Form for a new post to the db when one doesn’t already exist for the currently logged in user.

Hi Todd,

Ok, after working a bit more with this extension and using SAEF… I have run into a problem that I’m not sure how to solve.

As per this comment it looks like there’s a bug in the SAEF support, which probably crept in around the time Brandon started “officially” supporting SAEFs in FF (my original implementation was something of a hack).

It’s on the to-do list, but I’ve been on holiday for the past week. Hopefully I’ll get some time to work on this extension next week, and will be able to implement a fix.

In the interim, apologies for the inconvenience.

Cheers, Stephen

Sounds great Stephen. Thanks for your time on this… as I understand you are supporting an extension that you make no money with… which is pretty outstanding in itself.

I stand ready and waiting to beta test any fixes you publish.

Enjoy your time off.

Hi again,

I’ve got some problem with map that’s render to container with display:none (my map will be at one of tabs at page). It’s known issue (here and here) and solution for that is to refresh map after map tab is called or put the map container size when the map is creating (in js, something like {size:mew GSize(400,400)} during new GMap2 call - I hope you know what I mean, I’m not a js master 😊

Is it posible to pass the size of map or do a refresh on it without changing global_script.js?? I’m trying with that, but still now luck :(

Hello all,

Version 1.1.1 of the SL Google Map extension is now ready for download. Here are the highlights:

• “Map type” control added to maps in Control Panel.
• SAEFs now use the built in FieldFrame SAEF support (which wasn’t available when this extension was original built), and work swimmingly both for creating and editing entries.
• Various niggling bugs have been fixed, touch wood.

Before you upgrade to the latest version, I strongly suggest backing up your data. The new version stores map data in a different format (serialized array, as opposed to comma-delimited string), and performs some data conversion when the extension is upgraded. It’s worked fine for all my test installations, but better to be safe than sorry.

It’s also worth mentioning that SL Google Map now requires FieldFrame version 1.2.0 or above to function.

Let me know how you get on.

Cheers, Stephen

Hi Marcin,

I’ve got some problem with map that’s render to container with display:none (my map will be at one of tabs at page). It’s known issue (here and here) and solution for that is to refresh map after map tab is called or put the map container size when the map is creating (in js, something like {size:mew GSize(400,400)} during new GMap2 call - I hope you know what I mean, I’m not a js master Is it posible to pass the size of map or do a refresh on it without changing global_script.js?? I’m trying with that, but still now luck :(

I’m not quite following you here, but I do have a quick question / suggestion. If display:none is causing a problem, have you tried positioning the map off-screen, and repositioning it when the tab is clicked?

Stephen

Hi,

Sorry for my english :/

That’s exactly what I did for now - position absolute, and change it to static with the map tab on. And it works.

I’ve been trying all day with some refreshing, but couldn’t get it to work in 100% … so that’s why I asked you.

Thanks for help! your ext is just great, tomorrow I’ll try to upgrade to new version, and next week I’ll try to do some driving directions with it (hope will do that).

Hello all, Version 1.1.1 of the SL Google Map extension is now ready for download…

Thank you Stephen… yet again! Can’t wait to take it out for a run.

@MarcinM

Sorry for my english :/

No apology necessary. Your English is better than my anything other than English.

That’s exactly what I did for now - position absolute, and change it to static with the map tab on. And it works. I’ve been trying all day with some refreshing, but couldn’t get it to work in 100% … so that’s why I asked you.

At the moment, I think that might be your only option. Hope it works well-enough for you.

Thanks for help! your ext is just great, tomorrow I’ll try to upgrade to new version, and next week I’ll try to do some driving directions with it (hope will do that).

The extension doesn’t directly support driving directions, that’s slated for version 2. You can retrieve the pin location, and use that to query Google for the driving directions you require, but that would need to take place “outside” of the extension.

@Todd D.

Thank you Stephen… yet again! Can’t wait to take it out for a run.

You’re welcome Todd, hopefully it addresses the problems you were having.

Cheers, Stephen

Hi Stephen,

This is a great extension, and it will be super helpful for our editors once our new site launches. I’m having a problem though if I select not to show the map custom field by default. It seems like the map loads but it thinks that the window is much smaller; consequently, once I expand the field it only shows a map in the upper left corner (screen shot attached).

Have you encountered this before? I’m doing this on a local (OS X) development copy of EE (1.6.7). Everything seems to work fine if I set it to display the custom field by default. We’re not going to be using the map on every entry, though, so it would be nice if we could hide it.

Thanks! Jake

Hi Jake,

I’m having a problem though if I select not to show the map custom field by default. It seems like the map loads but it thinks that the window is much smaller; consequently, once I expand the field it only shows a map in the upper left corner (screen shot attached).

Sounds like you’re running into the same problem that Marcin described in this message, which is a known Google Map bug.

EDIT Just realised you’re talking about not showing the field by default in the CP (sorry, a bit slow this evening). I can’t think of a way around this, as it’s a problem with GM, rather than the extension.

Sorry about the negative response. If I think of a solution, I’ll be sure to let you know.

Cheers, Stephen

Hm okay. I had read Marcin’s post but I was not sure if it was the same problem because I want to hide the map on the publish page, not in my templates, but I see that it does have the same root cause in that Google Maps bug. I’m going to look into it further; I’ll let you know if I figure out any kind of solution.

Thanks, Jake

I can think of one potential solution, but I’m not entirely sure if this is possible because I’m not very familiar with extension development. But if there was a way for the SL Google Map to have it’s own show/hide preference (on a per map basis) rather than using EE’s default (which would stay on Show), it seems like it might be possible for it to load the map, and after that to trigger the hide toggle on the publish page. So it would not have to be hidden when the map loads, which would prevent the GM bug.

I really have no idea if this would be possible, and even if it is I’m not sure how hard it would be. I just wanted to throw the idea out there, I would love to know your thoughts.

EDIT

One additional note: it currently knows to reload the map if I resize the window. If the map is initially collapsed, and then expanded, and then the window is resized, the map reloads to the correct size and and functions correctly. Interestingly, though, it maintains the collapsed controls set (zoom arrows).