Stuart Silvester

You can use the camera app on a phone to scan the QR code, it'll give you a link that'll open the web browser/PWA to continue the check-in process. It's something we've discussed though! It's a nice idea, but Apple doesn't make it easy. You'd need an Apple Developer account to get the certificate required to sign the Pass for the Wallet. Yes, you can disable and enable certain features. Allowing Members to RSVP with guests for example can be disabled. You can also decide who can RSVP with category level permissions. It's not possible right now to collect additional data, only their name, phone and email.

Great!, we've been looking at performance improvements and there will be more in the next release too.

Any 8.x.x version should work, The form will tell you if you're using an unsupported version. We're preferring OpenSearch right now.

We replied to your ticket 30 minutes ago but haven't had a reply yet. Only you are having this issue right now, we haven't had any other reports. It looks like your upgrade may have been completed though.

It's a new index for this release. It might have taken a long time to execute which could cause the upgrader to go back to the prompt if it times out.

Thanks, I see what happened there. We'll get that fixed.

5.0.19 is now available!There's one very very small change since the last beta: #7226 Adds member_badge_awarded webhook

Yes, this isn't accurate. One of the uptime.com bots is getting caught up in a WAF block which is causing it to report everything down when all their other nodes can access without issue. We've identified and resolved the issue this morning.

5.0.19 Beta 4 is now availableWe 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 formFuzzy searching allows misspelled search terms to still return results. You can try it here: https://invisioncommunity.com/search/?q=microsooft&quick=1&

They will be new installs, we won't be importing any existing data. You'll be able to test that out on your own server during the beta process.

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

Later this year... 😁

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

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.

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.

If you use Chrome 128 on this community now, do you see any improvements?

Let me know if you're still seeing this. I have refreshed some data.

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.