SL Google Map Field Type : Google Maps in your CP, SAEFs, and EE templates : Now with map types in the CP
Development and Programming
Hi Michael,
I was just curious if you’re planning to, if at all, port this over as a field type for EE2.0’s new field-type API?
Yes, I am. The plan is to build a new version, with all the frequently-requested features, such as multiple pins on one map, and aggregate maps, and release it commercially for EE2.0.
Cheers, Stephen
Hey Stephen, I really appreciate the swift response.
Yes, I am. The plan is to build a new version, with all the frequently-requested features, such as multiple pins on one map, and aggregate maps, and release it commercially for EE2.0.
This is great news. This add-on is fantastic and I’m glad to know it will be available to use moving forward.
Thanks for the update.
Regards,
Michael
The plan is to build a new version, with all the frequently-requested features.
So just to remember my two requests:
driving directions - that would be just great to have this option I see it like: 1) at CP system admin sets 2 adressess and at front map is render with the directions 2) at CP system admin sets a B point and at front user can set A one via some address input, then press Search and gets a route to B Also would be great to have written directionf from google (the turn-by-turn) as an option to show at front.
custom pionter image
Greetings from Poland 😊
Firstly, many thanks to Stephen Lewis for a great plugin, I’ve just started out with EE and got google maps working on my site within a couple of hours. Also thanks to Mike Williams for his tutorial on adding multiple markers.
I’ve got one question about the markers though? Does anyone know if it is possible to add custom marker images to the google maps? The code I’m currently using to generate the markers is:
Many Thanks in advance.
Dougie
Hi Dougie,
I’ve got one question about the markers though? Does anyone know if it is possible to add custom marker images to the google maps?
You can hack it (which it looks like you’ve been doing), but the extension doesn’t currently support custom markers. As mentioned in some previous comments, version 2 will.
Cheers, Stephen
just a minor notice: GoogleMaps field-type does not work with jQuery Quick Save (v.2.0.3) well.
first time using this extension. It looks really nice. However, I keep getting the following error:
“This web site needs a different Google Maps API key”
I generated a new key about 4 different times. Any ideas?
@therooster
I generated a new key about 4 different times. Any ideas?
There’s probably a mismatch between the domain you generated the key for, and the domain you’re attempting to use it on. The API key is pretty specific, so subdomains and different ports can both trip it up.
@obsesif
just a minor notice: GoogleMaps field-type does not work with jQuery Quick Save (v.2.0.3) well.
OK, thanks for letting me know… have you noticed this being a problem with any other FieldFrame fieldtypes?
Stephen
nope, haven’t experienced any… got several of them already and checked them.
OK, I’ve made a note to check compatibility in future versions.
Cheers, Stephen
Hi, i’m getting this messages in SAEF with SL Google map field:
Notice: Undefined index: entry_id in /system/extensions/fieldtypes/sl_google_map/ft.sl_google_map.php on line 584
Notice: Uninitialized string offset: 0 in /system/extensions/fieldtypes/sl_google_map/ft.sl_google_map.php on line 594
Notice: Uninitialized string offset: 0 in /system/extensions/fieldtypes/sl_google_map/ft.sl_google_map.php on line 595
Notice: Uninitialized string offset: 0 in /system/extensions/fieldtypes/sl_google_map/ft.sl_google_map.php on line 596
Notice: Uninitialized string offset: 0 in /system/extensions/fieldtypes/sl_google_map/ft.sl_google_map.php on line 597
Notice: Uninitialized string offset: 0 in /system/extensions/fieldtypes/sl_google_map/ft.sl_google_map.php on line 598
Warning: Cannot modify header information - headers already sent by (output started at /system/extensions/fieldtypes/sl_google_map/ft.sl_google_map.php:584) in /system/extensions/fieldtypes/wygwam/ft.wygwam.php on line 348
Warning: Cannot modify header information - headers already sent by (output started at /system/extensions/fieldtypes/sl_google_map/ft.sl_google_map.php:584) in /system/extensions/fieldtypes/wygwam/ft.wygwam.php on line 349
Warning: Cannot modify header information - headers already sent by (output started at /system/extensions/fieldtypes/sl_google_map/ft.sl_google_map.php:584) in /system/extensions/fieldtypes/wygwam/ft.wygwam.php on line 350
Warning: Cannot modify header information - headers already sent by (output started at /system/extensions/fieldtypes/sl_google_map/ft.sl_google_map.php:584) in /system/extensions/fieldtypes/wygwam/ft.wygwam.php on line 351
Warning: Cannot modify header information - headers already sent by (output started at /system/extensions/fieldtypes/sl_google_map/ft.sl_google_map.php:584) in /system/extensions/fieldtypes/wygwam/ft.wygwam.php on line 352
Warning: Cannot modify header information - headers already sent by (output started at /system/extensions/fieldtypes/sl_google_map/ft.sl_google_map.php:584) in /system/extensions/fieldtypes/wygwam/ft.wygwam.php on line 353
Warning: Cannot modify header information - headers already sent by (output started at /system/extensions/fieldtypes/sl_google_map/ft.sl_google_map.php:584) in /system/extensions/fieldtypes/wygwam/ft.wygwam.php on line 348
Warning: Cannot modify header information - headers already sent by (output started at /system/extensions/fieldtypes/sl_google_map/ft.sl_google_map.php:584) in /system/extensions/fieldtypes/wygwam/ft.wygwam.php on line 349
Warning: Cannot modify header information - headers already sent by (output started at /system/extensions/fieldtypes/sl_google_map/ft.sl_google_map.php:584) in /system/extensions/fieldtypes/wygwam/ft.wygwam.php on line 350
Warning: Cannot modify header information - headers already sent by (output started at /system/extensions/fieldtypes/sl_google_map/ft.sl_google_map.php:584) in /system/extensions/fieldtypes/wygwam/ft.wygwam.php on line 351
Warning: Cannot modify header information - headers already sent by (output started at /system/extensions/fieldtypes/sl_google_map/ft.sl_google_map.php:584) in /system/extensions/fieldtypes/wygwam/ft.wygwam.php on line 352
Warning: Cannot modify header information - headers already sent by (output started at /system/extensions/fieldtypes/sl_google_map/ft.sl_google_map.php:584) in /system/extensions/fieldtypes/wygwam/ft.wygwam.php on line 353I should point out that it’s not EE SAEF but FoxEE Classified addon SAEF.
Any ideas?
Thanks
Hi Djive,
Some questions:
- Are you using the latest version of SL Google Map (v1.1.2 at time of writing)?
- Which version of FieldFrame are you using?
- Which version of ExpressionEngine are you using?
- Which version of PHP are you using?
- Are you trying to do something like this?
Cheers, Stephen
Hi,
- yes
- 1.3.4
- 1.6.8 20090723
- 5.2.11
- no, there is just one map on this page and i just put it’s shortname in the form like {lokacija}
This is the basic form code, i removed parts that were not important for this issue:
{exp:foxee_classifieds:post_form weblog="privatni_smjestaj_hrvatska" status="open"}
Naslov
<input type="text" name="title" id="title" value="{title}" size="50" maxlength="100"></p>
{lokacija}
<input type="submit" name="submit" value="Submit" />
{if no_results}
Please purchase a post product to use this form
{/if}
{/exp:foxee_classifieds:post_form}Cheers
Djive,
no, there is just one map on this page and i just put it’s shortname in the form like {lokacija}
This isn’t the correct syntax for the extension. As per the documentation, you’d need something like this:
{lokacija id="example-map" class="map" controls="zoom|scale|overview" map="drag|click_zoom|scroll_zoom" pin="drag|center"}
{map}This is the fallback content for users who cannot see the Google Map.{/map}
{/lokacija}You’d also need to specify a height for the map in CSS. For example:
#example-map {height : 250px;}If you still have problems using the above code, I’d suggest trying it in a standard SAEF, without the FoxEE tags. At least that way you’ll have a better idea where the problem lays.
Stephen
Hi,
that did not help, btw i could see the map and create a new entry successfully with just {lokacija}, the only issue are those notices.
I wish i could use standard SAEF but it’s not an option.
Thanks