It does seem to work with 3.2 at the moment, it hasn't been tested as such and isn't garaunteed to work, a release will come near to 3.2 release to ensure compatibility.
Member Map is compatible with IP.Board 3.0.0 upwards.
Have a look at this great installation guide: http://community.invisionpower.com/resources/articles.html/_/ipboard-3x/tips-and-tricks/how-to-installupload-an-application-r537
It applies to any applications.
It allows them to delete their own location, only super moderators and administrators can delete any location.
That information isn't stored at the moment.
Just looked, you've got the latest CSS, I wouldn't worry too much, if you click the marker again it will be fine. It only affects users with super moderator access.
On a side note, just noticed you're not that far up the A55/A548 from me.
Google only allow so many geocoding requests per hour from the Server. It could be possible, if you're on a shared host, that someone else also uses the geocoding functionality.
It's not a bug, it's a side affect of merging markers into one if they are placed in the same place. The Clustering system is 3rd party code, it only counts how many markers exist, it has no way of knowing that markers were merged (Since that is done in the back end)
Hi,
This was a reported bug in 1.0.3, http://ipb.silvesterwebdesigns.com/tracker/issue-9-extensionscoreextensionsphp-not-language-abstracted/
It was fixed in 1.0.4
Just updated with 1.0.4, forgot to add an enhancement to the list though! If there are multiple markers in one location, they will be merged into one marker now.
p.s., don't forget to revert template & css changes when upgrading (if you've modified the Map templates in the past)
Hi,
Sorry I missed that.
You would need to alter sources/classes/google.php around like 110.
change the IPSMember::load() call to include 'customFields', then your custom fields will be available for the skin to use