5.0.19 is Ready for Match Day

At the highest level, success is often decided by the smallest details.

A perfectly timed pass, A moment of composure. The tiny adjustments that separate a good performance from a great one.

Software development is often the same.

Major features often grab the headlines, it's the countless refinements behind the scenes that shape the day-to-day experience. The fixes that prevent a rare edge case. The accessibility improvements that make navigation easier. The performance optimizations that save a fraction of a second, thousands of times a day.

This release is full of those improvements, and unlike England at the World Cup, hopefully won’t fall apart after 60 minutes.

You can find the full change log here

Focused Beta Testing

This release contains significant changes to our OpenSearch and Elasticsearch integration.

We've moved to batched queue inserts to smooth out latency spikes and removed update_by_query operations during inserts, resulting in a more efficient indexing process.

If you're participating in the beta, we'd particularly appreciate testing:

• Search results and relevance

• Activity Streams

• Content indexing

• New content appearing in search

• General search performance under normal community activity

As always, thank you for helping us fine-tune the details before the final release.

@Stuart Silvester i see that there are a lot of fixes to Elasticsearch.

Can you confirm if this bug was fixed in this release?

Edited June 16Jun 16 by RevengeFNF

Just now, RevengeFNF said:

@Stuart Silvester i see that there are a lot of fixes to Elasticsearch.

Can you confirm if this bug was fixed in this release?

If you cannot replicate it on our site, then consider it fixed! There were some fixes to the unread functionality.

Just now, Matt said:

If you cannot replicate it on our site, then consider it fixed! There were some fixes to the unread functionality.

Ok, thank you. I will test it on my site when the stable release is out.

Updated. Thanks for the hard work!

This version supports Opensearch 2.x and 3.x.

For Elasticsearchg, it's the same 8.x versions or does it support the new 9.x version?

PS: For self host users, what is the recommended, Opensearch, Elasticsearch or it's basically the same?

1 hour ago, RevengeFNF said:

This version supports Opensearch 2.x and 3.x.

For Elasticsearchg, it's the same 8.x versions or does it support the new 9.x version?

PS: For self host users, what is the recommended, Opensearch, Elasticsearch or it's basically the same?

Currently, it's ES8 only. It will likely work, but we haven't fully tested it yet.

Opensearch is becoming more popular since it continues the open source project whereas Elasticsearch now as a proprietary license.

Gonna make me very happy... 2 of the 6or7 bugs/improvements to search i reported are in there.

#6995 Fix an issue where searching by titles only returned every post in a topic
#6996 Adjust links in search results to be more intuitive

Can you explain what the change is, as i did do a request for beter searching in private message.
The request was to be able to search in a message conversation. As it (5.0.18 ) now shows only the message the search term was found in, but it does not show where in the message.
Especially important, if you have 15pages of conversation.

#7007 Fix issues with searching the messenger folders

5 minutes ago, Stuart Silvester said:

Opensearch is becoming more popular since it continues the open source project whereas Elasticsearch now as a proprietary license.

Thanks.

If i switch to Opensearch from Elastic, will i notice any diference in performance or results, or it will be the same?

1 minute ago, RevengeFNF said:

Thanks.

If i switch to Opensearch from Elastic, will i notice any diference in performance or results, or it will be the same?

That's something I cannot answer, you would need to research the pros and cons of each platform.

supports PHP 8.4 ?

2 hours ago, Omri Amos said:

supports PHP 8.4 ?

5.0.x supports up to 8.3.

5.1 (in development) supports 8.5.

9 hours ago, Matt said:

5.1 (in development) supports 8.5.

Has an ETA been mentioned for 5.1?

8 hours ago, David.. said:

Has an ETA been mentioned for 5.1?

Later this year... 😁

Does anyone know when the theme editor will be fixed? It still doesn't work properly. I'm referring to my own changes added in the theme designer :/

3 hours ago, white020 said:

Does anyone know when the theme editor will be fixed? It still doesn't work properly. I'm referring to my own changes added in the theme designer :/

I've just responded to your topic there. There isnt actually a bug present. Its the way its being used. :)

Thank you for sorting out my license, so I can renew and remain active. 5.1 sounds exciting, and I look forward to its releae. @Ehren and the team have done a great job with it.

5.0.19 Beta 3 is now available.

Changes include:

#7159 Fix dropdown positioning in Chrome 125–128
#7166 Fix an activity stream performance regression introduced in 5.0.19 Beta

On 6/22/2026 at 4:00 PM, Stuart Silvester said:

5.0.19 Beta 3 is now available.

Changes include:

#7159 Fix dropdown positioning in Chrome 125–128
#7166 Fix an activity stream performance regression introduced in 5.0.19 Beta

I can't wait.

5.0.19 Beta 4 is now available

We didn't want to do a final release before a holiday weekend, so here's some small changes in the form of a new Beta.

#7190 Add optional fuzzy matching for OpenSearch searches
#7197 Added Two Factor Authentication to Lost Password form

Fuzzy searching allows misspelled search terms to still return results. You can try it here: https://invisioncommunity.com/search/?q=microsooft&quick=1&

Really looking forward to the stable release of this. It could solve "all" my problems :~)

5.0.19 is now available!

There's one very very small change since the last beta:

#7226 Adds member_badge_awarded webhook

I got this error while upgrading:

The log entry was triggered by a guest (Guests)
2 minutes ago
The URL of page the error occurred on was https://domain-here.org/admin/upgrade/?controller=upgrade&key=f1e4940614126e9773f110246f2825b1&mr=1&run_anyway=1&_=1783447364740
Type: upgrade_error

Error (1061) Duplicate key name 'index_search_created': addColumnsAndIndexes ["core_search_index",[],[{"type":"key","name":"index_search_created","columns":["index_hidden","index_date_created"],"length":[null,null]}]]

The upgrade went through, though.

The upgrade worked fine on my development install, but failed on my live site due to a missing database table, even though both upgrades were performed through the ACP:

CREATE TABLE IF NOT EXISTS `core_assignments_history` (
  `history_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT COMMENT 'ID Number',
  `history_assignment_id` bigint(20) UNSIGNED DEFAULT NULL,
  `history_date` int(11) DEFAULT 0,
  `history_by` bigint(20) UNSIGNED DEFAULT NULL,
  `history_type` varchar(20) DEFAULT NULL,
  `history_text` text DEFAULT NULL,
  PRIMARY KEY (`history_id`),
  KEY `history_assignment` (`history_assignment_id`,`history_date`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

After creating the missing table, the upgrade completed successfully.

Edited Tuesday at 08:55 PM5 days by Adriano Faria

7 minutes ago, Adriano Faria said:

The upgrade worked fine on my development install, but failed on my live site due to a missing database table, even though both upgrades were performed through the ACP:

CREATE TABLE IF NOT EXISTS `core_assignments_history` (
  `history_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT COMMENT 'ID Number',
  `history_assignment_id` bigint(20) UNSIGNED DEFAULT NULL,
  `history_date` int(11) DEFAULT 0,
  `history_by` bigint(20) UNSIGNED DEFAULT NULL,
  `history_type` varchar(20) DEFAULT NULL,
  `history_text` text DEFAULT NULL,
  PRIMARY KEY (`history_id`),
  KEY `history_assignment` (`history_assignment_id`,`history_date`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

After creating the missing table, the upgrade completed successfully.

Thanks, I see what happened there.

We'll get that fixed.