[XT] Membermap 1.0.2

[Mouth]

But maybe use the default XF User is active setting for this, to make the displays aligned.

Disagree. I think most/(all?) wouldn't want the Membermap to only display active users, but every user that has been active within the last 12 months (for example).

 

[Hoffi]

Active Users are members who are logged in the last 180 days.

That are the ones you can choose in the preview after typing an @ or which are listed in the list of todays birthdays. If there such an limit exists inside XF - and it does - it should not differ in multiple views.

We wll take your suggestion into our discussion.

 

[otto]

Bug:
URL is /xt-membermap/ but template xt_mm_index outputs canonical as /membermap

<xf:macro template="metadata_macros" name="canonical_url" arg-canonicalUrl="{{ link('canonical:membermap') }}" />

Realised/fixed because I added a route filter to change /xt-membermap to /membermap

If I understand you right, that works for me.

 

[otto]

I think most/(all?) wouldn't want the Membermap to only display active users, but every user that has been active within the last 12 months (for example).

No, not all - I am not. If, then as a optional setting.

 

[Mouth]

If I understand you right, that works for me.

Yes, me too. Is it intended the canonical URL is hardcoded and requires a route filter?

 

[mcatze]

Bug:
URL is /xt-membermap/ but template xt_mm_index outputs canonical as /membermap

It is just a typo issue, i fixed it in the next release.

 

[Mouth]

Suggestion:
Automatically turn-off marker clustering for zoom levels 15+. When you have multiple users with identical location values (and thus identical lat/long), it doesn't matter how much you zoom into the map the users will not be displayed and you only get a cluster value with no way to access whom are the users under this cluster. For example, this is zoom level 15 ...

 

[Mouth]

Active Users are members who are logged in the last 180 days.

Member Stats Birthdays ( /members/?key=todays_birthdays ) uses 365 days, as per src/XF/MemberStat/Birthdays.php

 

[Hoffi]

Probably. The Finder function isRecentActive uses 180 as default. Be sure we will perform something useful.

 

[mcatze]

Member Stats Birthdays ( /members/?key=todays_birthdays ) uses 365 days, as per src/XF/MemberStat/Birthdays.php

In RC3 there is an option to set the days of activity.

 

[mcatze]

@Mouth is that what you're suggesting?

 

[Mouth]

@Mouth is that what you're suggesting?

Looks great, thanks. I'd expect the max zoom to resolve the issue and enable users to be seen when many are clustered in the exact same lat/long.

 

[Hoffi]

Looks great, thanks. I'd expect the max zoom to resolve the issue and enable users to be seen when many are clustered in the exact same lat/long.

I am afraid, id the lat/long is exact the same, the pins will be stacked.
But I have an idea, that the user can move their pin to be more precise.

 

[Mouth]

I am afraid, id the lat/long is exact the same, the pins will be stacked.

GitHub - jawj/OverlappingMarkerSpiderfier: Deals with overlapping markers in Google Maps JS API v3, Google Earth-style

Deals with overlapping markers in Google Maps JS API v3, Google Earth-style - jawj/OverlappingMarkerSpiderfier

github.com

 

[Triops]

@CrispinP solved the problem in his map for xf 1.5 by somehow adding a little variance to the pins when they were all in the same place (here are some pins for "Berlin" without detailed addresses):

 

[mcatze]

mcatze updated [XT] Membermap with a new update entry:

Update to v1.0.1 RC3

Fixed:​

• Issue during Rebuilding MapData
• Delete locationData and minimap if:
  • delete user
  • change user group (without perm)
  • user ban
  • user disabled
• some code tweaks

Added:​

• User activity as option for showing on map
• MaxZoom und minCluster for Clustering
• switch to two different api entrys 'cause api restriction for public api key
• acp user action for delete minimap
• rebuild mapData for...

Read the rest of this update entry...

 

[mcatze]

@Mouth & @Triops is this something you can agree with?

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

 

[Mouth]

@Mouth & @Triops is this something you can agree with?

That works great!

 

[Mouth]

mcatze updated [XT] Membermap with a new update entry:

• switch to two different api entrys 'cause api restriction for public api key

Read the rest of this update entry...

Not working correctly ...



Google Maps API Key has been set with restrictions for the 3 API's listed, and server IP addresses
Google Maps JavaScript API Key has been set with restriction for the 1 API listed, and domain referrer ( .mydomain.com/ )

With Google Maps JavaScript API Key empty, still get the error.
Google Maps API Key needs to also have Google Maps JavaScript API active, otherwise error above

Google Maps JavaScript API Key with a key value, gives error above.

 

[mcatze]

The Google Maps API is pretty difficult. I will take a look if i found something. Please check also your restrictions again.