-
-
Feature Request for Cloud - Enable AI Blocking
For ChatGPT/OpenAI, they have several different bots/crawlers. - https://developers.openai.com/api/docs/bots ChatGPT-User is allowed; that's the bot that will fetch data in response to a specific question. Typically, where this data is used, there is a link back to the page.
-
Feature Request for Cloud - Enable AI Blocking
Hi Chris, We do utilise Cloudflare Enterprise on all Cloud communities to block AI-related bots. Some, such as the 'User' bots, are allowed, but the majority of the AI crawling and AI search bots are blocked. Google is an exception because they use the same user-agent identifier for normal search crawling and AI crawling, although you could block this with a custom robots.txt. Are you seeing high guest traffic from a specific IP/Bot?
-
Stuart Silvester started following 5.0.17 is now available! and Feature Request for Cloud - Enable AI Blocking
-
-
-
-
5.0.17 is now available!
Yes, I think we'll get to a point where we need to do that. A good example is MySQL 9.6, which removes (by default) the SHA1 and MD5 functions. However, we need to be smarter about it; an upper limit or specific supported versions would most likely block MariaDB versions (because they're so much higher). That would be problematic.
-
5.0.17 is now available!
This is how it works now. The problem is that < 5.0.16 didn't have the concept of a maximum or supported versions. It would only check that you had a minimum of X version. As you've seen some comments here, those using 5.0.17 with PHP 8.4 are blocked from upgrading to 5.0.18 until they fix the version issue.
-
5.0.17 is now available!
I should have clarified, by saying we'll be supporting PHP 8.5, I was also implying PHP 8.4 support at the same time. It'll be later this year. I've deployed an upgrade blocker for v4. Your AdminCP has told you for years that PHP 8.0 will not be supported in a future update. 8.0 and 8.1 are end-of-life and should be considered insecure.
-
5.0.18
This is an important security update addressing two issues. Cloud customers already have this update applied; you may need to run the upgrade process when you next visit your community.
-
4.7.24
This is an important security update addressing two issues. Additionally, this release adds support for PHP 8.2 and fixes issues with using Stripe in the AdminCP. Invision Community 4 will be discontinued on 31st December 2026, with security updates provided until then. Cloud customers already have this update applied; you may need to run the upgrade process when you next visit your community.
-
Stuart Silvester reacted to a post in a topic:
Spring Update: Changes coming to Invision Community this month
-
5.0.17 is now available!
I think I've mentioned this elsewhere, but it's part of the transition to a different way of specifying version requirements. Previously, we'd have a minimum and a recommended, but that doesn't always work when there's a major new PHP release that introduces a backwards incompatibility (which happens more often now). This release introduces the 'new way' where the release specifies exactly which PHP branches are supported. Unfortunately, PHP 8.4 isn't included in that, but we're working on compatibility with PHP 8.5. We've also introduced new development processes to ensure any new code written is compatible with all of our targeted PHP versions, including nightly PHP builds. This will allow us to support new PHP versions more quickly in future.
-
5.0.17 is now available!
5.0.17 has been released!Changes since the last beta include: #6884 Add hover effect to mention dropdown #6886 Ensure "Continue Shopping" button closes its dialog #6887 Ensure animations finish running in Safari and Chrome.
-
5.0.17 is now available!
I cannot reproduce any issues with the color fields, and it looks like they're working in your screenshot too.. Can you provide further information about the issue you're experiencing? Make sure you're using a supported PHP version too. We cannot help you if you're using an unsupported version.
-
5.0.17 is now available!
5.0.17 Beta 3 is here!Changes in this beta include: #6850 Fix Helpful recount failing when item doesn't exist #6852 Ensure mentions dropdown works in dialogs #6853 Ensure quoting works in topics #6854 Updated select menu backgrounds #6860 Ensure posts are rendered after pagination in Safari #6865 Allow SSO buttons to bypass form validation
-
5.0.17 is now available!
Obviously, we wouldn't recommend making changes to this. 8.4 isn't supported at this time. We'll be going straight to 8.5 support in the coming months. We're working to improve processes to keep up with new PHP releases. Thanks!. We'll look into this.
-
5.0.17 is now available!
Sometime later...
-
5.0.17 is now available!
The bug report is still open. There has been some discussion on it, but it seems to be linked to a larger, more complex issue. Unlikely. Betas are for fixing high-impact issues (e.g., issues where the user cannot register because the CAPTCHA cannot be completed) or issues introduced in earlier betas. I have noticed this too. I was surprised how often I use it!
-
-
5.0.17 is now available!
5.0.17 Beta 2 is now available!Changes since Beta 1: #6829 Ensure hCaptcha is shown correctly in dialogs #6830 Ensure active pagination buttons can be hovered #6832 Fix assignments when there’s no assignment container #6837 Fallback to empty object if stream_classes is null #6838 Fix JS error when replying to new topic with featured first post