Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simplemap and Neo #21

Closed
JoshAinsworth opened this issue Dec 5, 2016 · 2 comments
Closed

Simplemap and Neo #21

JoshAinsworth opened this issue Dec 5, 2016 · 2 comments
Labels

Comments

@JoshAinsworth
Copy link

Hi,

I've come across a minor edge-case bug when dealing with neo and simplemaps. If you have a simplemaps field that is both on an entry and inside a neo field on the same entry, the first field fails to load the google map whilst the one inside the neo field is fine... If that makes sense.

@dreamseeker
Copy link

Hi,

I had the same problem in neo of the entry editing form.
It seems to be a cause that SimpleMap cannot acquire hideMap's right value in both SimpleMap_MapFieldType.php and map-fieldtype.twig.

@Tam Tam added the bug label Mar 8, 2017
Tam added a commit that referenced this issue Mar 28, 2017
- Added [FeedMe 2](https://sgroup.com.au/plugins/feedme) support! (thanks to @engram-design, #23)
- Added support for [Neo](https://github.com/benjamminf/craft-neo). #21
- Fixed when using the address search, locations that are non-specific (i.e. the name of a country) will no longer be forced to be specific.
- Fixed "Unnamed Roads" no longer change to a different unnamed road when the map is re-loaded. #26
- Disabled scrollwheel on map, #27
- Details about the selected location are now populated server-side, no more JavaScript shittery! #30
- Improved locale specific address details #24
- If the query limit is reached, the map will re-try after 1 second, a maximum of 5 times. #19
- The address of the map will be returned when output as a string, i.e. `{{ entry.myMapField }}`. #29
@Tam
Copy link
Member

Tam commented Mar 28, 2017

This should be fixed in v1.5.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants