Matt

Hi Kate, You can submit a ticket via the client centre: https://invisioncommunity.com/clientarea

Yeah, good idea that.

CSS is per-theme, but you can add it into the AdminCP > Theme area too.

As above, most AI bots are allowed to crawl much like search engines. There are a few specific ones (Claude, etc) that consume a lot of resources when they're directed to a website, so those are blocked for now. We are looking to bring a MCP server and extended AI access for an additional monthly fee to cover the increased database/origin hits.

Was it this? https://invisioncommunity.com/4guides/themes-and-customizations/template-syntax/introduction-to-template-syntax-r137/

The simplest way would be to use member groups to create a group that has access to courses, and then get Zapier to change their member group on purchase/expiration.

Thats a CSRF key mismatch. It might occur if the user does not have javascript enabled.

It can be done without any custom coding. All you need to do is use Group Promotions. Rename your "Members" group to "Onboarding". When members sign up, they are put into the onboarding group with very little permission. You can use a Pages page as the default page for the Onboarding group which states they need to do a course to complete their onboarding. Then, create a new group called "Members with all the permissions relevant for them. Use Group promotions to move members from Onboarding to Members once they complete the course. That's it! It'll then move members when the course is completed while restricting access to the full content of your community.

You could use alerts: https://invisioncommunity.com/docs/staff-moderation/the-moderator-cp-r154/#6-alerts

Hi Steve, Elasticsearch was forked by AWS into Opensearch when Elasticsearch changed from open source. There are a few variances, including the document format, which means that technically, our Elasticsearch extension is now for Opensearch. This means that it's unlikely in the short term that we'll update Elasticsearch, but we will very likely update Opensearch. A quick test looks like we just need to remove the maximum version check and it'll be fine on 3.x.

I manually moved some content around when we restructured the forums, which seems to have.. broken something. I'm rebuilding the index now.

This is an area we have plans to improve. Our current search implementation is based on database lookups which is fine, but given the advances in intelligence, it's fair to want something more. As always, cost is a big driver of decisions. We could easily and quickly build a connector to a popular AI engine to vectorise and pull results but on large communities with hundreds of thousands of posts and content that would eat tokens and burn through money in no time. I ran the numbers quickly and to store in a vector database and fetch the top 50 matches using an AI agent such as Claude, it'd cost around $200/month for a 500k post database. That'd get you a quick solution but a very expensive one. We also have complications such as our rich permission functionality, our comprehensive search filters and the activity stream which uses the same underlying technology. Essentially, we'd have to strip back some of the stream features and pull out the text and put that elsewhere. The short version is - we're on it but it won't be something that's coming in a minor release and it'll likely be offered as a paid option for our Cloud customers. In the short term, if you could share what you're trying to search for, then there may be ways to squeeze more out of our current system.

They switched things around so their Fanatec brand got an independent community. We obviously cannot say too much but that's the outcome.

It's here: https://forum.fanatec.com We have have many enterprise clients that we are partners with. This entails regular calls, project management, etc. We do not advertise them outside of the logos unless we request a case study (Gatorade). There are NDAs in place for most of them.

I speak to LEGO every week, they have a community for their local user groups.

I can't promise detailed docs on the PHP framework, but there's room for improvement on a lot of other areas.

Yeah good idea, I'll sort that. The native menu manager can handle that as it can show/hide based on permissions.

It depends. 🤔 Community in the context of supporting a product, such as this one, is a resource that doesn’t need to be a top level item. But we may change some of the navigation around as we settle in with it. There a fair few improvements to be made with community navigation and the user icons. It’ll take a few days to get to it.

There are pros and cons. I feel that feedback is slightly different between client cohorts but we will monitor and if it feels like a single shared area is a better fit then we can merge them back into one. The classic label refers to the style of licensing and has been so for a good few years. Segmenting client cohorts makes sense given how we have a sizeable group of customers that have never had the on-premises version and this is growing faster than the licensed customers. We’re not trying to phase anyone out, it’s just a necessary move to reduce confusion across the community.

As you may have noticed, we've had a shuffle around on the community. There is a clearer separation between Invision Community Classic and the Invision Community Cloud areas, with a shared area here. This change allows both sets of clients to discuss things that matter to them without confusion over which version of Invision Community the conversation starter is using. It's natural that Invision Community Classic owners who are responsible for their servers have a different set of needs than someone using our platform who wishes to get more configuration advice and general guidance. If you own both products, then feel free to post in the area that is relevant to the needs of that community.

Fixed

Our long overdue website refresh is now live! Invision Community 5 was released well over a year ago and our website was still focused around v4 and its features instead of talking about the benefits of the Invision Community platform. It also did not promote what we're doing very well. We're fortunate to work with brands of all sizes, alongside passionate independent community owners and we're trusted to help guide strategy and develop features inline with the needs of communities at scale. Beyond that, some of the most exciting work we're doing for enterprise clients has the forum element as one part of the bigger picture. Some are building the community around events, others content and one around a creator/influencer portal. Our strength is how much functionality you get in the box, how extensible it is, and our in-house talent. Our headline of "Community at our core, built for so much more" is something we'll lean into as the website matures. We feel that we are uniquely positioned to build a multitude of experiences around community because our platform is much more than a forum system. We'll be moving the community navigation into the community area, I know accessing streams is a bit cumbersome right now with it being in the main navigation. We'd love to hear your feedback and any issues you come across.

No. Extensibility is a big part of our strength.

I made it clear that Invision Community Classic is still part of our future. Very few customers have any modifications. The two things are not linked.

It’s largely down to where the community market is going. There is nothing stopping developers from launching their own site and marketing it. We are not blocking developers from building custom experiences. 5.1 will be our next release.