Matt

Invision Community 5.1 has been quietly in development for a while now, and brings many exciting things such as ⬛⬛⬛⬛⬛⬛⬛⬛⬛ and ⬛⬛⬛⬛⬛⬛⬛ It's worth noting that 5.0 to 5.1 is not a major leap, in the way that 4.x to 5.0 was, but there are several major 'things' along with a slew of improvements to key areas. We're at the point where enough has been finished that we're ready to get some early testing and feedback. How to applyAll you need to do is register your interest in this topic. We can't take everyone on, we're really looking for around six to begin with and you'll be testing on a new Cloud site pre-loaded with 5.1 Alpha. I'll contact those via DM with instructions on what to do next. Allow us a few days to wait for enough replies before we contact you. We'll aim to get going within the next few weeks. Thanks!

It's the first logo that is the issue.

We will be monitoring it closely.

We're yet to see any real plan or legislation from the Government (and won't for many months) but the Australia ban does not include "text heavy platforms" such as Discord, so I see no reason that forums as a whole will be included in a ban, but as always, it depends on the contents of your forum. https://www.esafety.gov.au/about-us/industry-regulation/social-media-age-restrictions/faqs#which-platforms-are-age-restricted

5.0.x supports up to 8.3. 5.1 (in development) supports 8.5.

If you cannot replicate it on our site, then consider it fixed! There were some fixes to the unread functionality.

It's not even our retail cloud plans. It's rarely used honestly and there are better ways of doing it in v5.

I'd really like to find a way to share the same comment stream between both.

It's mostly for our internal teams to use in a pinch, we generally create apps to make use of the listener/widget/events system.

Pages is one of Invision Community’s most powerful features, allowing easy creation of blogs, knowledge bases, documentation, bug trackers and more. With the new Workflow Manager, it just got a whole lot more powerful. WorkflowsWorkflows enable you to perform multiple actions from a single button, triggered by criteria you define. For example, staff can process, approve, reject or update records with a single click, rather than manually working through several steps. This video walks you through setting up "Approve" and "Reject" buttons in a bug tracker. Match CriteriaWhen you create a workflow, you define the match criteria that control which records show the button. In our video, the "Approve" button should only appear on newly submitted bug reports. Once a report is already approved or closed, the button is no longer relevant, so it simply does not show. Criteria can be based on the item's status (hidden, pinned, featured, and so on) or on the value of a custom field, giving you precise control over when each workflow is available. ActionsThe next step is to configure the actions that fire when the button is clicked. You can mix and match as many as you need: Post a reply on the record Change the value of a custom field Change the item status (pin, hide, feature, and so on) Notify the item author Notify specific members Assign the item to a member or team If any action needs input from the person running the workflow, such as writing a custom reply, a small dialog will prompt them before the actions run. Putting it togetherWith the buttons configured, a single click can mark a bug report as accepted, post a public reply for the author, and fire a webhook to create an issue in GitHub automatically as every time a workflow runs, Invision Community fires an event, meaning you can connect workflows to external tools and services without writing any custom code. Beyond a bug trackerWorkflows are available for any Pages database. An approval process for submitted articles, a content review pipeline for a knowledge base, or a simple "mark as resolved" button for a support request database are all straightforward to set up. If you use a database to manage form submissions, a single workflow can update multiple fields and send a notification to whoever needs to take action next. Workflows are available for Creator Pro, Teams, Business and Enterprise. View full blog entry

Manual PHP is available on Enterprise.

The Page Builder makes it easy to create attractive pages with widgets, custom HTML and Invision Community data. One of the most-used block types is the custom HTML block, which lets you drop markup anywhere on a page. However, if you want to use the same design in multiple places, perhaps a feature card, a promotional banner, or a testimonial, you have to create a separate block each time and maintain them individually. Template Blocks solve that. How Template Blocks workA Template Block combines a custom HTML template with a set of fields you define. Instead of hardcoding the content, your template uses placeholders. Each time you place the block on a page, you fill in the fields and the template renders with that content. Setting one upStart by creating a new block and choosing the Template Block type. Define the fields you need such as a heading, an image URL, a short description, whatever your design calls for. Write the HTML template, using the field placeholders. as Save the blockOnce saved, it works like any other block in the Page Builder. Drop it onto a page, click Edit, fill in the fields and save. Drop it again somewhere else and give it completely different content. A practical exampleSay you have a "Featured Member" card used in several places across your community. With a Template Block, you design the card once and fill in a different member's name, photo and bio each time you place it. Update the card's design and update every instance accordingly. Template blocks can be a great way to simplify the number of blocks you have, and make it much easier to edit once on the page in the future. We would love to hear how you use Template Blocks in your community. Share your ideas in the comments below. View full blog entry

Yes, you could create a Pages page and use that, with anything you want embedded via a HTML widget. Or you could create a database and use that to hold the contact requests, and set up any custom fields you need and edit the form template (if required).

I can reply in more detail later, but this is a fairly common request. You can use javascript to detect the browser language of the person viewing, so you could create a little HTML widget with just javascript in it to detect the browser's language, if it doesn't match the current language, display a modal/box on the page to offer them to go to the correct page.

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.