jezzdk / statamic-google-maps Goto Github PK

There is no option to disable show styles button in pro edition

Adding the icon-tag returns an error.

{{ map icon="/assets/marker.png }}

Error message: Modifier [icon] not found

Project details:
Statamic 3.3.3 Pro
Laravel 8.83.5
PHP 8.1.2
doublethreedigital/duplicator 2.1.1
jezzdk/statamic-google-maps 1.2
spatie/statamic-responsive-images 2.11.0

Thanks!

Hey, could you add the possibility to show the controls please? This would be really nice!

The icon for the "Find my location" button on the map in the control panel is incorrectly sized and covers a large portion of the map. This is occurring in Firefox but not in Chrome.

Chrome:

Firefox:

Hi there

Would like to place multiple markers on the same map using this addon - is this possible. Don't mind paying for the pro version if that is a pro feature.

Thanks

All control panels stick in the top left corner. Check attached screenshot. I am using the Google Maps Pro version.

Project details:
Statamic 3.3.3 Pro
Laravel 8.83.5
PHP 8.1.2
doublethreedigital/duplicator 2.1.1
jezzdk/statamic-google-maps 1.2
spatie/statamic-responsive-images 2.11.0

Thanks!

After searching for an address using the geocoder the marker is placed on the map in the control panel. Save the page, reload the editor and the marker is gone.
Now I have to manually click the map for the marker to be placed / saved.

After a geocoder search:

After saving and reloading:

Google has made changes to loading the google maps api and now displays the following message:

https://developers.google.com/maps/documentation/javascript/overview?hl=es-419#Loading_the_Maps_API
https://developers.google.com/maps/documentation/javascript/advanced-markers/migration?hl=es-419

Thank you so much for this addon!

The addon uses the env() function in files other than config files. If the config:cache command is used, the env() function call returns null so the map never loads correctly.

From Laravel documentation:
"If you execute the config:cache command during your deployment process, you should be sure that you are only calling the env function from within your configuration files. Once the configuration has been cached, the .env file will not be loaded and all calls to the env function will return null."