The Doors Are Open

The stage is set. The lights are on. The final preparations are complete.

After months of development, testing and sharing what's coming, we're ready to open the doors to Invision Community 5.1. Today we're releasing the first beta of 5.1.0. It brings new ways to run events, build and sell courses, offer premium content.

We've also made significant improvements to performance and accessibility, along with plenty of other changes throughout the platform

This is a beta, so there is still testing and polishing to do. We'd love to hear what you think as we work towards the final release of 5.1.0.

Key changes include:

• Complete event management.

• Email Drip Campaigns (Professional, Business, Enterprise).

• UI Updates including accessibility and performance improvements.

• Limited Content Views.

• Courses improvements (Creator Plus, Professional, Business, Enterprise).

• Tag restrictions and suggestions.

• Staff Points boost and points per day limits in Achievements.

We recommend using the beta on test communities and waiting until later in the beta process to update production communities.

You can find the full change log here.

😍

Nice! Good work everyone. I tried to upgrade but ran into the error "There are no applications available to upgrade".

I don't know if it's supposed to be like this, but after the update the custom template colors stopped working.

Also see this error since recently:

SELECT s.* FROM cloud_quests_scorecards AS s  LEFT JOIN cloud_quests AS q ON s.score_quest_id=q.quest_id WHERE s.score_member_id=1 and s.score_status=0 and s.score_dismissed=0
IPS\Db\Exception: Unknown column 's.score_dismissed' in 'where clause' (1054)
#0 /var/www/html/5010003/system/Db/Select.php(402): IPS\Db->preparedQuery('/*b334808::b334...', Array, true)
#1 /var/www/html/5010003/system/Db/Select.php(460): IPS\Db\Select->runQuery()
#2 [internal function]: IPS\Db\Select->rewind()
#3 /var/www/html/5010003/applications/cloud/sources/Quest/Quest.php(741): IteratorIterator->rewind()
#4 /var/www/html/5010003/applications/cloud/extensions/core/Loader/forumsFrontForumsTopic.php(81): IPS\cloud\Quest::activeQuests()
#5 /var/www/html/5010003/system/Dispatcher/Front.php(186): IPS\cloud\extensions\core\Loader\forumsFrontForumsTopic->js()
#6 /var/www/html/5010003/system/Dispatcher/Dispatcher.php(129): IPS\Dispatcher\Front->init()
#7 /var/www/html/5010003/index.php(16): IPS\Dispatcher::i()
#8 {main}

Edit: thanks for the quick fix!

Edited September 30Sep 30 by Cedric V

22 hours ago, white020 said:

I don't know if it's supposed to be like this, but after the update the custom template colors stopped working.

I've opened a bug report for this so we can investigate further.

Are the reactions configurable as to how they work?

I don't want to click twice to add a default reaction.

Now I need to click, aim, and click again.

9 hours ago, Square Wheels said:

Are the reactions configurable as to how they work?

I don't want to click twice to add a default reaction.

Now I need to click, aim, and click again.

They are not configurable, no

Do third-party apps created for 5.0.20 stop working in 5.1.0?

24 minutes ago, beats23 said:

Do third-party apps created for 5.0.20 stop working in 5.1.0?

That really depends on what your third party app does.

We had to update many method signatures for compatibility with newer PHP versions. If an app overloads any of those then it will likely need updating.

13 hours ago, Square Wheels said:

Are the reactions configurable as to how they work?

I don't want to click twice to add a default reaction.

Now I need to click, aim, and click again.

This change is to make it more mobile friendly, and to make it more accessible for screen readers.

14 hours ago, Square Wheels said:

Are the reactions configurable as to how they work?

I don't want to click twice to add a default reaction.

Now I need to click, aim, and click again.

You need to click twice to react to a post? That has always been the case, hasn't it?

Edited October 2Oct 2 by My Sharona

Was anything changed with JS/jQuery in 5.1?

Edited October 2Oct 2 by Cedric V

Is there an option in the Theme Editor or elsewhere that I may have missed to make menus open automatically on hover like they did in 5.0? None of the menus work that way anymore, either on the front end or in the ACP. Now I need an extra click just to do anything.

Edited October 2Oct 2 by Adriano Faria

Uncaught ReferenceError: _ is not defined
front_front_widgets.js?v=d815db93211790928383&csrfKey=&antiCache=d815db93211790928383:8

18 minutes ago, Cedric V said:

Was anything changed with JS/jQuery in 5.1?

I tested a couple of apps just to see how it behaves, and it doesn't work in either of them.

It should display the time remaining.

Edited October 2Oct 2 by Adriano Faria

Yes there are several things broken. Some of my apps will need to some work. Notifications are also broken. Quotes are broken. 😬

47 minutes ago, My Sharona said:

You need to click twice to react to a post? That has always been the case, hasn't it?

No, you could easily click on the first icon.

2 hours ago, Matt said:

This change is to make it more mobile friendly, and to make it more accessible for screen readers.

I assumed it was something like this.

Yes, first world problems, but it's a lot more clicks now to do anything that I could just hover over before, like the profile hover.

29 minutes ago, Cedric V said:

Was anything changed with JS/jQuery in 5.1?

Yes https://invisioncommunity.com/release-notes-v5/510-beta-1-r55/

Ah, a bit of a fair warning to remove underscore JS was welcome. :) But I guess it's my fault not looking into the changelog.

Just now, Cedric V said:

Ah, a bit of a fair warning to remove underscore JS was welcome. :) But I guess it's my fault not looking into the changelog.

Not sure what warning was needed there. We're still in beta :)

Why did you remove profile information from mobile devices?

2 minutes ago, Marc said:

Not sure what warning was needed there. We're still in beta :)

Beta release doesn't justify a removal of underscore which many apps rely on. But maybe that's me. Like I said, my fault not looking into the changelog and noticing a removal like underscore JS. If I had known, I wouldn't have upgraded, but silly me on a day where I didn't think about it.

16 minutes ago, Cedric V said:

Beta release doesn't justify a removal of underscore which many apps rely on. But maybe that's me. Like I said, my fault not looking into the changelog and noticing a removal like underscore JS. If I had known, I wouldn't have upgraded, but silly me on a day where I didn't think about it.

It was removed in 5.1 from the first alpha. The release notes have all the details.

18 hours ago, Cedric V said:

Beta release doesn't justify a removal of underscore which many apps rely on. But maybe that's me. Like I said, my fault not looking into the changelog and noticing a removal like underscore JS. If I had known, I wouldn't have upgraded, but silly me on a day where I didn't think about it.

We also talked about it in a news article in August:

And removed most of our usage in March, but left the library in place until a bigger release (5.1)

5.X.0 releases are where we're going to make bigger changes like this, it's the right place to do it.