Martin A.

If you want to add support for it, the repo is accepting pull requests. https://github.com/MartinAronsen/membermap

Send me the URL to your site, as well as login credentials for a test account in a private message, and I'll have a look.

Sorry for the delay guys. I believe I have found the issue with the task. If there were 0 locations found in the current batch it was processing, the task would turn itself off, as well as turn the "Import markers" setting off. I have changed this now to not turn it off until all members have been processed. After updating, go into Member Map settings and re-enable the import option, then run the task manually, and report back what you got back from it. It should now say "Synchronised X out of Y member locations", where Y should be a much greater number than what you had in the past. If should also keep going even if X is 0, as long as Y is greater than 0. Did you select a result in the dropdown first? Behind the scenes there are hidden input field for the coordinates, and those aren't populated until you select an item in the autocomplete result. For those having issues with the queue, where it kept on running; I haven't been able to reproduce this error myself. This queue isn't intended to be used before you have close to 4000 markers, as that's when I started getting "out of memory" issues. I have now hardcoded this to not run at all if you have less than 1000 markers. There is a calculation done when deciding to use the queue or do it instantly ( Total memory limit - Memory already used < ( Total markers * 0.01(MB) ) + 10MB ). If the amount of memory we assume we're going to use is greater than what we have left, the queue is used. These numbers may not have been available on shared hosting or CIC, and that might be the reason why a member with less than 50 markers is set to use the queue. I'll push the update to the marketplace in a bit, but I'll wait a few days before I trigger the ACP update notification.

Post a link to your site here, or send me a personal message.

@Pablo BJB and @nylyon, try the version I just uploaded.

If it's fixed now I'm not going to look further into this. In order to do so I would need to know the content of the "Message" field in the log entry as well, as that contains the actual error message too. How many markers do you have, btw? It shouldn't use the queue unless your server is low on memory (PHP's 'memory_limit') or you have more than 4000 markers.

Will if successfully build the cache when you run it manually? Can you have a look in the system log in the ACP to see if you find anything that related to this?

Oh, so you upgraded the whole software from 3.4.6 yesterday? Or you upgraded/installed Member Map and it took the marker data from a 3.4.6 database/table? That can explain any weirdness.

That's weird. I see that it appears as if all markers were added 12 hours ago too, is that correct? Have you done any imports or anything? What version did you upgrade from? Yes, you can delete the duplicated markers from that section.

Are the markers duplicated in the database too? Click Browse Markers, and have a look. If they're not this is a cache issue. Rebuild both server and browser cache.

Thanks for letting me know. I've uploaded a repacked version, as the first one was compressed in the TAR format (but named .zip),

v3.5.2 have been uploaded fix the issue with merging members.

Add the following to your custom.css body[data-pageapp="membermap"] .leaflet-top.leaflet-right { display: none; }

Because their Nominatim policy does not allow the kind of usage Member Map require. And when I initially developed this 3 years ago, I used a different API endpoint at MapQuest. If I remember correctly, there was also a difference in the results from OSM Nominatim and MapQuest Nominatim, where the latter was far better at getting addresses. This may of course have changed over the years. https://operations.osmfoundation.org/policies/nominatim/ And they're not happy about automated bulk requests, which the profile sync feature would violate.

Hello, What you're missing here is that popup content is loaded with AJAX (this was done to reduce the size of the cache). See \IPS\membermap\modules\front\membermap\ajax getPopup(). You can do this in the template: {{if $marker->container()->type == 'member'}} {{$profileFields = $marker->author()->contentProfileFields();}} {{error_log( print_r( $profileFields, 1 ) );}} {{endif}}

Hi, You can add that table as a DB join. $db = \IPS\Db::i()->select( '*', array( 'membermap_markers', 'mm' ), array( 'mm.marker_member_id=? AND mm.marker_parent_id=?', intval( $memberId ), intval( $groupId ) ) ); $db->join( array( 'core_ofields_content', 'pc' ), 'mm.marker_member_id=pc.member_id' );

Google Maps is not used at all in this app.

Go to the Activity Streams settings (Think it may be ACP > Discovery > Streams > Activity Stream Settings). Then toggle off the checkboxes until the error disappears, if it even does. That should show what area it may be failing on.

When looking at this again, why do you blame this app? It's not even mentioned in the error stack trace, nor does the error appear in this app. The code it errors on is an area not used by this app either.

Hi, you can update to v3.2.1, https://invisioncommunity.com/files/file/3070-member-map/?changelog=14763. That's the last version for the 4.1 series, and I believe it fixes your error. If you don't have permission to post in anty of the available group they will be grayed out. And the members category is a special type of category, which you can't move markers too. And thanks for the requests, but I just don't have the time right now to add new features to this app.

Yes, it is. UPDATE membermap_markers SET marker_last_comment=marker_added WHERE marker_last_comment < 1 OR marker_last_comment IS NULL

Can you run this query for me? SELECT COUNT(*) FROM membermap_markers WHERE marker_last_comment < 1 OR marker_last_comment IS NULL "marker_last_comment" should be the same as "marker_created" is there are no comments on the marker. This is set by the framework upon creation, so there might have been a bug in the past.

With GDPR watching over all of us right now, there is no way I can do this legally with the default being opt-in. I would think a horizontal widget for those who don't have a marker, or where the marker hasn't been updated in a while will be just as powerful. The lack of pins in your map boils down to marketing and making users aware of the feature. Force adding unaware users is not the solution.

Then I'm not sure why it fails. Can you take a look in the error log too? And perhaps try a different application? I've just installed this successfully on two different servers.

This might be a stupid question, but you did extract the zip file you downloaded, and then uploaded the membermap.tar file to your communities?