Hey team, it's been 84 years (if you know you know), but...

We're excited to announce that Invision Community 4.6.0 Beta 1 is officially live! 🎉 

@Matt has a blog post on the way detailing all of the amazing additions, including how many commits and lines of code that were changed. A lot. The answer is a lot. 

Just to refresh your memories, some of the biggest changes/additions include:

• Achievements (Points!)
• Web app and Push notifications
• Anonymous Posting when posting as a member
• Highlight Topics with replies from specific Groups
• Spam Improvements
• (And more!)

It's available per request for Cloud customers or, if you're self-hosted, by manually downloading it.

Self-hosted: please make the necessary backups before upgrading. Because this is a Beta, please understand there is an inherent risk when upgrading.

The more information/feedback we get, the better we can optimize and improve things 🙂

If you find something and would like to submit a bug, please do so here.

Looking forward to hearing what you think! Sound off in the replies below. 

Can't wait to check it out!

Edited May 18, 20213 yr by StormyWays13

Very, very impressed with achievements. 

Two things I love.

1/ The ability to reward activity by location. This will allow me to award, for example, VFX Expert status to members who post best answer n times in a VFX Q/A forum.

2/ And the following I can see being incredibly popular. My wife was thrilled with it.

 

One small request for future updates:

Please would you consider grouping achievements by named group (same way as you do with custom block authoring) and rendering them to the front end in separate containers identifiable by user nominated class or group name. This will allow us to, optionally, visually separate loyalty type rewards (for example logs in 10 times) from proficiency awards such as receiving an expert award in a video editing Q/A forum.

Either way, very happy with what I have seen so far. Installed on a test server without a hitch and so far I have only seen one small issue with VideoBox custom fields which has been reported to the author.