Your November release is ready for testing!

A version that ends in .13 released just before Halloween is some coincidence. Let's hope it's lucky for all!

This is our monthly updates and improvements release. You can see the full changelog here.

Key changes include:

• New: Automatically lock large topics and start a new one.

• New: Ability to customise or disable the "Welcome" email when a member registers.

• Updated: Editor QoL improvements.

Let us know how you get on!

Great stuff! Upgraded like a charm.

Installed on dev -testinstall. No problems during upgrade. No errors in logs.

Edit:
Can you explain what the Editor QoL improvements are?

Edited October 28, 2025Oct 28 by Moestuin

2 hours ago, Moestuin said:

Edit:
Can you explain what the Editor QoL improvements are?

You can see them in the changelog: https://invisioncommunity.com/release-notes-v5/5013-beta-1-r47/

#5836 Bugs/tiptap nov release
 - Issue #5488: Content Editor not remembering selecting language
 - Issue #5545: Default box color not working
 - Issue #5541: Boxes sometimes have two titles
 - Issue #5552: Pasting text into spoiler collapses it
 - Issue #5587: Spoiler button visible while "Can use content boxes" set to "Never"
 - Issue #5658: Autosave draft message not persisting
 - Issue #5553: Safari crashes when adding a new line between spoiler and image

Ok then it seems there are only bug fixes and no QoL improvements.

25 minutes ago, Moestuin said:

Ok then it seems there are only bug fixes and no QoL improvements.

Tell that to the people experiencing the bugs

Not debating that fixing these bugs directly improves the stability and reliability of the product, ensuring a better user experience. But it is important to recognize that these are genuine bugs that negatively impact the user experience, and fixing them is essential for the product’s quality and usability. Therefore, these updates are primarily bug fixes, not QoL improvements. As QoL improvements suggests new enhancements that make the product easier, more convenient, or more pleasant to use, involving new features, UI tweaks, or usability improvements that do not directly fix bugs or resolve crashes.

Anyway thats my point of view QoL vs Bug fixes. When i update my site, i can tell there are a lot of bug fixes to the editor. And not merely copying and pasting what was marketed for this update. Thanks!

19 hours ago, Matt said:

• New: Automatically lock large topics and start a new one.

• New: Ability to customise or disable the "Welcome" email when a member registers.

Q: How do these work? Are the in the Mod Panel, or admin settings somewhere?

1 hour ago, Moestuin said:

Ok then it seems there are only bug fixes and no QoL improvements

There are a couple not noted in the changelog which are QoL in regards to the code editor

• IPS template highlighting is supported in the monaco-based code editors

• When multiple languages are supported, code editors can dynamically determine which language is used. They will also remember user selections

• Content in code editors is saved as a draft between reloads before submitting.

What about Ehren's fixes for last iOS? Are they included?

7 minutes ago, bags_ppp said:

What about Ehren's fixes for last iOS? Are they included?

Are you referring to https://invisioncommunity.com/forums/topic/484973-meatball-failure-after-upgrade-to-5012?

That should be covered by

#5820 Ensure dropdown menus work inside forms

Beta 2 is here!

#5892 Fix an issue where running images through the profanity filters can return a null value
#5894 Move follow popup language string to core

2 hours ago, Stuart Silvester said:

Beta 2 is here!
#5894 Move follow popup language string to core

Thank you for the above fix... 👍

Does the new patch fix the issue I reported as well?

On 10/28/2025 at 5:24 PM, Matt said:

• New: Automatically lock large topics and start a new one.

On 10/29/2025 at 1:20 PM, James Hargreaves said:

Q: How do these work? Are the in the Mod Panel, or admin settings somewhere?

Sorry, I'm still struggling to find any settings for this anywhere?

1 hour ago, Askancy said:

Does the new patch fix the issue I reported as well?

It looks like my colleague reopened a ticket for you on that one

40 minutes ago, James Hargreaves said:

Sorry, I'm still struggling to find any settings for this anywhere?

We're going to blog about this. Its an automatic thing, rather than something you have to set

I’m curious about the new functionality for automatically splitting large topics. A few questions come to mind. How large are these topics supposed to be? Won’t such a split risk breaking the topic’s coherence? How will users know that they should post in the new topic? I understand the purpose behind this, but I’m concerned about the user experience.

When I read Editor QoL Improvements, I became very excited! This is it! Finally!

But sadly no.... 🥹

2 minutes ago, The Old Man said:

When I read Editor QoL Improvements, I became very excited! This is it! Finally!

But sadly no.... 🥹

I don’t think it was a priority. I’ve also been waiting for a few versions now for the fix related to showing “0” in the notification count, but sadly not this time either.

1 hour ago, PanSevence said:

I’m curious about the new functionality for automatically splitting large topics. A few questions come to mind. How large are these topics supposed to be? Won’t such a split risk breaking the topic’s coherence? How will users know that they should post in the new topic? I understand the purpose behind this, but I’m concerned about the user experience.

I will do a blog post but the short version is this:

By default, topics will be split when they reach 100,000 replies.

The moderators will see a warning indicating this will happen.

A task runs to lock and create a new topic, with links back to the previous part.

You can adjust the threshold where topics are split, you can do so by using the following constant:

define( "LARGE_TOPIC_LOCK", 1000000 );

1 hour ago, Marc said:

We're going to blog about this. Its an automatic thing, rather than something you have to set

Ahh, excellent - thank you!

Edited October 30, 2025Oct 30 by James Hargreaves

On 10/29/2025 at 5:00 PM, Stuart Silvester said:

Are you referring to https://invisioncommunity.com/forums/topic/484973-meatball-failure-after-upgrade-to-5012?

That should be covered by

#5820 Ensure dropdown menus work inside forms

But now is not working on Firefox Android. 😔

Menu disappears immediately after clicking on the three dots.

@Ehren

It does work on old posts but not on the new posts which is most common scenario beaczse people usually want to edit and fix errors.