Version 4.7.8 Beta 2

PHP8 Compatibility Scanner

Edited March 3, 20231 yr by Chris Anderson

43 minutes ago, Chris Anderson said:

Version 4.7.8 Beta 2

PHP8 Compatibility Scanner

Oops sorry, I uploaded the wrong archive. Try again now.

On 5/6/2022 at 3:23 PM, Chris Anderson said:

@Andy Millne It would be nice to be able to exclude certain members from appearing in the Connections app or if that isn't possible at least allow us to exclude members from certain selected groups from being listed in the app. 

Would you have time in the near future to address the issue above?

18 hours ago, Chris Anderson said:

Would you have time in the near future to address the issue above?

Actually yes, I have a few hours today so will see what I can do.

I've just uploaded a new version (1.3.0) to the marketplace that includes support for excluding user groups from Connections results.

 

Please look into why your app is causing the error below and fix it.  Thanks...

 

I've submitted a new minor version release (1.3.1) that should resolve this. thanks for letting me know.

@Andy Millne Unfortunately, when I upgrade to 1.3.1 the site goes offline:

I also got a message from Plesk that the site is offline.  So whatever change you made is not playing well with the site.  I disabled the app and things go back to normal.  Reenabled it and things go amiss.  I also cleared the system caches. 

No errors are being logged in the ACP and the PHP8 Compatability Scanner notes no problems.

I went ahead and disabled your app on my test server while waiting for you to figure out what needs to be fixed.  Plesk sent me an email that the site is back online.

Edited June 12, 20231 yr by Chris Anderson

@Chris Anderson I've re-uploaded 1.3.1 with another change that should resolve that but if not could you please PM me access so I can investigate?

@Andy Millne The latest uploaded version seems to have corrected both issues.  Thanks for posting such timely updates.

On 3/14/2022 at 7:59 AM, Andy Millne said:

It matches cases where multiple users leave positive reputation on the same content. The more content you both like the more the algorithm will weight you as having similar interests.

For example if you and I both like the same five topics we will be more likely to show to each other than someone else that has only liked two of the same topics.

The algorithm does not distinguish between different reaction types. It responds to all positive reactions regardless of the specific reaction given. e.g. you may react with a "like" and I may react with "haha" but as they are both positive interactions then the chance of us sharing similar interests is higher.

@Andy Millne I do not see any tasks created that relate to this app.  Did you add additional functionality to an existing task?  If so which one? 

I'm trying to gauge the impact this app might have on a server.  If you have a site with tens of thousands of members all reacting positively to each other how will that impact a site's CPU, memory, and database size?

If a particular member gets a bunch of new likes from other members today how long will it take before they show up in "Similar Interests"?

 

 

38 minutes ago, Chris Anderson said:

@Andy Millne I do not see any tasks created that relate to this app.  Did you add additional functionality to an existing task?  If so which one? 

I'm trying to gauge the impact this app might have on a server.  If you have a site with tens of thousands of members all reacting positively to each other how will that impact a site's CPU, memory, and database size?

If a particular member gets a bunch of new likes from other members today how long will it take before they show up in "Similar Interests"?

The similar interests uses the indexed core_reputation_index table, it doesn't use a task. I've tested this on some very large data sets and don't see any big performance hits that require it to be pushed off to a task. It means the data is real time too.