Stuart Silvester

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.

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?

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.

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.

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.

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 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.

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 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

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.

Sometime later...

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 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

Great, thank you. The good news is that we've already fixed this for beta 2 (I merged in the fix a few minutes ago!)

Ah, I see where the confusion is. The Editor to add comments is on the comment tab. Thanks, I can reproduce this too.

I have tested on multiple installs and cannot reproduce this. I have the editor as expected. Do you have any errors in your browser console?

Thanks, I've created a bug report for this. I cannot reproduce this issue. Do you have any specific steps that I can try?

Yes, it's exactly that. It isn't a self-hosting vs Cloud thing. We have features on higher-tier plans that are not on lower tiers.

Invision Community 5.0.17 SPRINGS into life This is our monthly updates and improvements release. You can see the full changelog here. Along with the usual fixes, we've got new features in this update: PagesWorkflow Manager(Creator Pro, Team, Business, Enterprise) This is an exciting one!. Workflow Manager is designed to streamline and automate repetitive actions. This range of Pages updates are designed to save time and reduce repetitive tasks. Each database has a "Workflows" menu item in the AdminCP. Each created workflow is displayed as a single button. You can define the properties of the button, and you use "Match Criteria" to determine when the button should show, and "Actions" to determine what it does when clicked. For this series of screenshots, I have two workflows set up, one to approve and one to reject the article. The status field itself is configured so it cannot be changed outside of a workflow. Available Match Criteria Item Status - pinned/featured/hidden/etc. Custom Field value (uses OR logic, not AND) (match criteria is the same for both workflow actions) Available Actions Assign an item Post a comment Change the item status - pinned/featured/hidden/etc. Notify the item author Notify specific members Change the value of a Custom Field This configuration gives us two new buttons on the article. Let's click approve this and send a message to the author. There's a huge number of Workflows that could be implemented. Let us know what flows you're thinking about automating. Reusable Template BlocksThis new block type allows you to define a set of input fields and a template to reuse multiple times. Create your new block with the template structure of your choice. On the front-end, you can add the new block to the page using the Page Editor. Fill in your fields for this block location and hit save! You can use the same block as many times as you wish on the same page. This screenshot shows two blocks using the same pre-defined template. Field TemplatesCustom display formats for fields can now be saved as a template. This allows multiple fields to share the same display formatting without copying and pasting the setting on each field. This also has the advantage of being able to update templates using the Pages template manager. Status FieldA minor, but time-saving, new feature is the status field. Out of the box, it allows you to specify the statuses and an associated color which are automatically displayed on the record without any further configuration. Status fields are integrated with the new Workflow Manager, allowing these fields to be automated. Other smaller, but notable changes: We added a new setting to allow archived topics to instruct search engines not to index them (they're also removed from the sitemap). Continued modernization by removing reliance on 2 more JavaScript libraries. Further improved accessibility on the registration form (password strength is now announced by screen readers). Focused Beta Testing We'd love it if you could pay some extra attention to these areas during the beta process. Removed underscore.js usage in favour of native JavaScript equivalents Underscore was used extensively in our code, leading to widespread adjustments to remove reliance. Please let us know if you see any JavaScript errors. Preparing for jQuery 4.0 We have made many changes to remove reliance on deprecated jQuery functionality to prepare for jQuery 4.0. Please let us know if you see any JavaScript errors.

You'll only need the one webhook with the correct URL. You can delete both, then go to Commerce in the AdminCP, edit the PayPal Gateway and save it without any changes; this will recreate the webhook with the correct configuration. We're only seeing subscription data being sent to the wrong URL at this time.

Go to https://developer.paypal.com/ and have a look at Event Logs > Webhook Events. These logs should tell you more information about the requests sent to Commerce. I have had a look at our logs for PayPal requests. It looks like your webhook URL isn't quite right. It starts with /forum/, but you'll need to edit the webhook and remove that so the URL starts with /applications/nexus

5.0.16 is now available!There are some minor changes since the previous beta: #6706 Improved Voice Over alerts with registration form errors #6710 Update UnderscoreJS to 1.13.8