Martin A.

We did 🙂 Gotta spend some to earn some. If the income isn't enough to cover the cost you are either not here for the money, don't have a big enough demand, or not pricing it "correctly".
Keep in mind that this also ensures that you can't purchase from someone who have left the "scene", leaving you with a file that will probably not be supported. Should it be taken over by someone else, you will most likely have to purchase it again.
This is not true anymore. An app or plugin would be compatible with the entire major version ( 4.x ) in the beginning of the 4 series. In the past few years changes to a central method signature happens more often, breaking backwards compatibility, even if it's "correctly made". They are even introducing brand new functionality in the middle of a major version. So there could be stuff out there that is compatible with 4.6.x but not 4.6.y.
This is stuff they wouldn't have done back in the days.
This is why we, the 3rd party developers, have to keep our licenses up to date to keep up with these changes.

If you need this for development purposes you can use this constant
define( 'DEV_DISABLE_ACP_SESSION_TIMEOUT', TRUE ); That'll disable the timeout when IN_DEV.

No need to edit template. Custom field would do the same 😉

Pay attention to Default Value! It has to be filled out in order of the field to be displayed.
 

 

Edit the database template Displate -> Record
Add this anywhere (change the 200 to what you believe the 'words per minute' speed is for someone reading):
{{$wordCount = \str_word_count(\strip_tags($record->_content));}} {{$estimateTime = \ceil ($wordCount/200);}} Then add this in your desired place in the template:
Estimated reading time: {$estimateTime} minutes  

Just FYI, if a dev does NOT RENEW their "package" - whatever it is, the MP stuff is, apparently, automatically deactivated.
Esther (Headstand) just let her package lapse and is renewing this week. She's not going anywhere.

Just a follow up for those who may have had the same problem as me, the "Community Map" creates a menu tab at time of import and or installation, so go to your menu, and you'll see it.
Thanks Martin for maintaining this application, and yes, it's about time you get paid for it!

This issue has been resolved in 4.6.10 beta 1. Feel free to give this a try, or await the full release if you prefer

Thank you for letting us know, this will be fixed in an upcoming release.

How is Community Map displayed? Does it over ride Member Map? I can find my Member Map page, but not the Community Map. I've imported Member Map data successfully I think, I really won't know till I see the Community Map, if I can find it. Thanks
EDIT: Never mind, found it. 🙂

$recordClass::getItemsWithPermission( [ [ "`cms_custom_database_{$record::$customDatabaseId}`.`category_id`=?",$record->container()->id ] ], ... ) This should work

I have tagged our developers in to review this. If this is a bug here we can get this logged and resolved

Updated a forum to 4.6.9 yesterday, and at the same time updated Elastic to the highest supported version - 7.16.3.
Woke up to lots of these errors in the log caused by a stream periodically fetched as RSS.
 
[error] => Array ( [root_cause] => Array ( [0] => Array ( [type] => x_content_parse_exception [reason] => [1:8714] [bool] failed to parse field [should] ) ) [type] => x_content_parse_exception [reason] => [1:8714] [bool] failed to parse field [filter] [caused_by] => Array ( [type] => x_content_parse_exception [reason] => [1:8714] [bool] failed to parse field [should] [caused_by] => Array ( [type] => illegal_state_exception [reason] => expected value but got [START_ARRAY] ) ) ) The issue in the JSON appears to be here:
{ "bool": { "should": [ { "bool": { "filter": [ { "terms": { "index_class": [ "IPS\\forums\\Topic\\Post" ] } }, { "terms": { "index_item_id": [ 657215, .......... 785214 ] } } ] } }, [<--- HERE, this is 1:8714 { "terms": { "index_author": [ 61654, 151262, 204067, 204990, 272358, 503699, 554475 ] } } ] ] } }, The latter "terms" should not have been in brackets.
This is caused by too many array()'s added to the condition in Elastic\Query.php
/* Are we including content posted by followed members? */ if ( $includeMembers and $followed = iterator_to_array( \IPS\Db::i()->select( 'follow_rel_id', 'core_follow', array( 'follow_app=? AND follow_area=? AND follow_member_id=?', 'core', 'member', $this->member->member_id ), 'follow_rel_id asc' ) ) ) { $conditions[] = array( array( 'terms' => array( 'index_author' => $followed ) ) ); } I've removed one of those arrays and that seems to have solved the issue.

Updated a forum to 4.6.9 yesterday, and at the same time updated Elastic to the highest supported version - 7.16.3.
Woke up to lots of these errors in the log caused by a stream periodically fetched as RSS.
 
[error] => Array ( [root_cause] => Array ( [0] => Array ( [type] => x_content_parse_exception [reason] => [1:8714] [bool] failed to parse field [should] ) ) [type] => x_content_parse_exception [reason] => [1:8714] [bool] failed to parse field [filter] [caused_by] => Array ( [type] => x_content_parse_exception [reason] => [1:8714] [bool] failed to parse field [should] [caused_by] => Array ( [type] => illegal_state_exception [reason] => expected value but got [START_ARRAY] ) ) ) The issue in the JSON appears to be here:
{ "bool": { "should": [ { "bool": { "filter": [ { "terms": { "index_class": [ "IPS\\forums\\Topic\\Post" ] } }, { "terms": { "index_item_id": [ 657215, .......... 785214 ] } } ] } }, [<--- HERE, this is 1:8714 { "terms": { "index_author": [ 61654, 151262, 204067, 204990, 272358, 503699, 554475 ] } } ] ] } }, The latter "terms" should not have been in brackets.
This is caused by too many array()'s added to the condition in Elastic\Query.php
/* Are we including content posted by followed members? */ if ( $includeMembers and $followed = iterator_to_array( \IPS\Db::i()->select( 'follow_rel_id', 'core_follow', array( 'follow_app=? AND follow_area=? AND follow_member_id=?', 'core', 'member', $this->member->member_id ), 'follow_rel_id asc' ) ) ) { $conditions[] = array( array( 'terms' => array( 'index_author' => $followed ) ) ); } I've removed one of those arrays and that seems to have solved the issue.

Updated a forum to 4.6.9 yesterday, and at the same time updated Elastic to the highest supported version - 7.16.3.
Woke up to lots of these errors in the log caused by a stream periodically fetched as RSS.
 
[error] => Array ( [root_cause] => Array ( [0] => Array ( [type] => x_content_parse_exception [reason] => [1:8714] [bool] failed to parse field [should] ) ) [type] => x_content_parse_exception [reason] => [1:8714] [bool] failed to parse field [filter] [caused_by] => Array ( [type] => x_content_parse_exception [reason] => [1:8714] [bool] failed to parse field [should] [caused_by] => Array ( [type] => illegal_state_exception [reason] => expected value but got [START_ARRAY] ) ) ) The issue in the JSON appears to be here:
{ "bool": { "should": [ { "bool": { "filter": [ { "terms": { "index_class": [ "IPS\\forums\\Topic\\Post" ] } }, { "terms": { "index_item_id": [ 657215, .......... 785214 ] } } ] } }, [<--- HERE, this is 1:8714 { "terms": { "index_author": [ 61654, 151262, 204067, 204990, 272358, 503699, 554475 ] } } ] ] } }, The latter "terms" should not have been in brackets.
This is caused by too many array()'s added to the condition in Elastic\Query.php
/* Are we including content posted by followed members? */ if ( $includeMembers and $followed = iterator_to_array( \IPS\Db::i()->select( 'follow_rel_id', 'core_follow', array( 'follow_app=? AND follow_area=? AND follow_member_id=?', 'core', 'member', $this->member->member_id ), 'follow_rel_id asc' ) ) ) { $conditions[] = array( array( 'terms' => array( 'index_author' => $followed ) ) ); } I've removed one of those arrays and that seems to have solved the issue.

https://invisioncommunity.com/clients/purchases/ and click on the renew option for the resource.

Edit the template "popupContent" in communitymap > front > map. Remove all occurrences of the following
target='_blank'  That should do it for you 🙂
Do the same in the other *Popup templates in the same folder to change the behavior in other marker types.

I have identified a PHP 8 issue with the template you mentioned, and a fix for it is about to be submitted. 

Oh man, thanks @Martin A.!
I wasn't aware PhpStorm could do that!

You don't need that other program if you already have and use PhpStorm. Ctrl + Shift + F will give you an equal solution 🙂 

Yup, that did the trick.  Thanks!
 

Yes, the admin can override these permissions and choose specific groups to view:

That was it!  Initially, I did as you described, but the Community Map tab remained hidden, until I unchecked all in the Content tab.  Bit weird, but I got what I needed, a group of non-moderators being able to edit markers they haven't created themselves.
 
Cheers!

The color inside the marker cluster should use the site's default text color. which in your case is light gray due to the black background. I'm fixing this now 🙂 
Looks like your site has an issue fetching the javascript files needed for the day/night. It may temporarily fix itself if you disable the feature in the settings. 
I'm fixing this now by fetching this file from a 3rd party CDN instead.
You should see a button on top of the settings page, like this

It should be visible even though the API field is empty. No need to fill that out anyway, and that too will be converted from Member Map.
This is technically true. But it would only cause an error if someone were to manually manipulate the URL to fetch a marker that doesn't exist. Fixing this now.

Did the final migration to the 4.6 version today ... movement of all the old data and settings went flawlessly .... 
New product is great .   No issues at all !!

Because now the other file is failing... I'll put up an update in a few minutes.