SeNioR-

Reporting it as it just occurred on my live site...
UPDATE `core_members_known_ip_addresses` `core_members_known_ip_addresses` SET `ip_address`='' WHERE ip_address != '' AND last_seen <1709136738 IPS\Db\Exception: Duplicate entry '0138fdaa72c8135e62b3487f5be7b11d-2970-' for key 'PRIMARY' (1062) #0 /home/fbaeefdf/live.ynwa.tv/system/Db/Db.php(1159): IPS\_Db->preparedQuery() #1 /home/fbaeefdf/live.ynwa.tv/applications/core/extensions/core/IpAddresses/Logins.php(33): IPS\_Db->update() #2 /home/fbaeefdf/live.ynwa.tv/system/Member/Member.php(6504): IPS\core\extensions\core\IpAddresses\_Logins->pruneIpAddresses() #3 /home/fbaeefdf/live.ynwa.tv/applications/core/tasks/pruneipaddresses.php(43): IPS\_Member::pruneAllLoggedIpAddresses() #4 /home/fbaeefdf/live.ynwa.tv/system/Task/Task.php(281): IPS\core\tasks\_pruneipaddresses->execute() #5 /home/fbaeefdf/live.ynwa.tv/applications/core/modules/admin/settings/advanced.php(751): IPS\_Task->run() #6 /home/fbaeefdf/live.ynwa.tv/system/Dispatcher/Controller.php(107): IPS\core\modules\admin\settings\_advanced->runTask() #7 /home/fbaeefdf/live.ynwa.tv/applications/core/modules/admin/settings/advanced.php(38): IPS\Dispatcher\_Controller->execute() #8 /home/fbaeefdf/live.ynwa.tv/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\admin\settings\_advanced->execute() #9 /home/fbaeefdf/live.ynwa.tv/admin/index.php(13): IPS\_Dispatcher->run() #10 {main} I believe this is a knock-on effect of it NOT having been pruning the IP addresses correctly previously - the issue you'll have is that there could be multiple entries for a specific device_key and member_id, but with different IP addresses. Now that task has been fixed to do the pruning, when it tries to remove the IP address on those multiple entries, the PRIMARY key for each row will end up being the same as the key is made up of device_key, member_id, IP address (which is now blank)
Sample content attached:core_members_known_ip_addresses.sql
When the query in the task runs against that data, the error occurs:
UPDATE `core_members_known_ip_addresses` `core_members_known_ip_addresses` SET `ip_address`='' WHERE ip_address != '' AND last_seen <1709135288
 
 

This is fixed in 4.7.16.

I'll be disabling that functionality until this is resolved then...just been alerted to a data leak (title of a private topic being visible) which is going to cause a few problems now that it's been seen.
Test of a topic in a private forum, viewable by a normal member...
 

will try tomorrow

Optimize your forums, guys. Interaction to Next Paint (INP) is an official Core Web Vital.
INP replaced First Input Delay (FID) as the new responsiveness metric. Chrome is officially deprecating support for FID, so developers and site owners have until September 9, 2024, to transition over to INP.
 

You also need to upload the files to the server before clicking Continue. Have you done that step?

Not at present for subscriptions, but we do have this in version 5 🙂 

I am trying to install the new security patch on my software and I'm not able to do so. I'm including the errors I'm getting in screenshot form.
I downloaded the package as it asked me to, and when I click Continue, I get the error in the next screen.

It was used for guest page caching in earlier versions. It's no longer used in current releases.

I updated to 4.7.16 and see the same. Members can’t post in a club database category, even though they can post on the database page itself. Admins/club owners can post. 

Please install the latest beta, rather than beta 1. We are a few versions in

There is some unused code in the Authy handler file /system/MFA/Authy/Handler.php in the verifyApiKey() function at the end of the file:
public static function verifyApiKey( $val ) { try { return \IPS\Http\Url::external("https://api.authy.com/protected/json/app/details")->setQueryString( 'api_key', $val )->request()->get()->decodeJson(); } catch ( \IPS\Http\Request\Exception $e ) { throw new \DomainException( $e->getMessage() ); } if ( !$response['success'] ) { throw new \DomainException( $response['message'] ); } }  
The IF after the TRY/CATCH is never executed, it either returns inside the TRY or throws an exception in the CATCH:
if ( !$response['success'] ) { throw new \DomainException( $response['message'] ); } It can be removed.

Kind of.

@Matt Finger is working hard on it as we speak. I don't want to say too much but we did a lot of research and picked the best solution in terms of development, stability and future functionality. More news soon. It's probably one most have never heard of but it is used widely. If anyone is worried about us using Froalo or TinyMCE, don't be. 😅

My oh my, how exciting

We looked at Quill, but no.

🤔-Thinking about the bug
👀-Looking for the solution to the bug
📰-Writing the fix for the bug
➡️-Exiting when he realised the bug fix didnt work
👤-Hiding in the shadow to see if anyone notices
 

I want to thank @teraßyte for outstanding guidance.
We were able to complete the upgrade from an outdated community forum from 4.2 to 4.7+ with his support.
His service is top notch and I highly recommend reaching out to him for help.
Respectfully,
Shyrax

I can’t wait for the new bumpin’ music track!

Quick, let's try to find clues in Matt's emojis 👀

New feature blog early next week. 🤔👀📰➡️👤

@Marc Stridgen the devil tempted me to try to do it manually 😈
UPDATE core_members SET signature=REPLACE(signature, '/uploads/monthly_','/monthly_'); UPDATE core_message_posts SET msg_post=REPLACE(msg_post, '/uploads/monthly_','/monthly_'); UPDATE forums_archive_posts SET archive_content=REPLACE(archive_content, '/uploads/monthly_','/monthly_'); UPDATE forums_posts SET post=REPLACE(post, '/uploads/monthly_','/monthly_'); UPDATE core_member_status_replies SET reply_content=REPLACE(reply_content, '/uploads/monthly_','/monthly_'); It came out fine. I marked for myself about 100 places where there was this problem, and everywhere is in good
 
Thanks to everyone for your help. The topic can be closed

Is there any approximate release date for version v5 yet?

Yeah, IPB5 will be pretty sweet, from what I can tell.  Looking forward to seeing more from the team.  I find it extremely satisfying to see how active the developers are making a difference in our communities.  Also heavy involvement with us is key and you are hitting that nail on the head too.  Much appreciate everything you guys are doing!!

Eagerly awaiting the annoucements @Matt !

4.7.16 is currently in beta.  Once it is released, the issue should be fixed.  🙂