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.

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.

15 hours ago, Marc said:

Because of the very reason you stated there. Its not yet general availability. We would only work on PHP versions once they have been fully released. At that point, the software needs to be tested alongside those versions, things changes as needed, and those changes applied to a new version of the invision community platform. So you wouldnt see compatibility immediately as the PHP version is released. Its actually very rare you will see that in any software.

Thanks for the clarification, that makes sense. I'll wait for 5.1.0 final and its PHP 8.5 support.

5.1.0 Beta 2 is now available!

Changes since Beta 1

#7634 Display reactions in a more compact UI on mobiles
#7636 Fix editor lockup when quoting on Android Chrome
#7637 Reduce Tiptap typing lag from quote layout and node-view effects
#7640 Fix issues with showing relative dates
#7645 Fix issues with loading custom theme settings.
#7649 Fix error closing follow modal
#7653 Underscore References and Old Bundles
#7654 Added header hooks
#7658 Fix multiquote button reloading the page
#7661 Fixed blog dropdown menus
#7665 Let the editor toolbar stick on content forms.

You may notice the Editor being a bit snappier in this release, especially when working with large quotes.

Sometimes reactions do not work on desktop neither here nor my community.

About the reaction icons, why is it you have to "Change reaction", every time you want to react to a comment? As i did not already react to the comment, so there is nothing to change. But always have to "change my reaction" to click on time extra to put a reaction on the post.

Really annoying to have you now have to click two times, for something simple that used to work so easly in the past.
Don't give me an awser like, touche screen. As i don't have a touchscreen. Device Profiles should solved these issues, and present a workable solution to the device that a user is using.

Edited October 11Oct 11 by Moestuin

This code restores the hover effect for reactions. Add to Theme Designer: Core CSS & JS

;(function () {
    'use strict';

    // Extend the native controller, including reactions added by AJAX.
    ips.controller.mixin('reactionHover', 'core.front.core.reaction', true, function () {
        const initialize = this.initialize;

        this.initialize = function () {
            initialize.apply(this, arguments);
            if (this._singleReaction) {
                return;
            }

            const button = this._reactButton[0];
            const menu = button && document.getElementById(button.getAttribute('popovertarget'));
            if (!menu || typeof menu.showPopover !== 'function') {
                return;
            }

            const desktop = window.matchMedia('(hover: hover) and (pointer: fine)');
            let openedByHover = false;
            let closeTimer;

            this.on('pointerenter', '[data-role="reactionInteraction"]', function (event) {
                const pointerType = event.originalEvent?.pointerType || event.pointerType;
                if (!desktop.matches || pointerType !== 'mouse') {
                    return;
                }

                clearTimeout(closeTimer);
                if (menu.matches(':popover-open')) {
                    return;
                }

                const previousFocus = document.activeElement;
                // i-dropdown focuses its first item. Hover should keep the current focus.
                menu.addEventListener('toggle', function (toggle) {
                    if (toggle.newState !== 'open') {
                        return;
                    }
                    window.requestAnimationFrame(function () {
                        if (!openedByHover || !menu.contains(document.activeElement)) {
                            return;
                        }
                        if (previousFocus === document.body) {
                            document.activeElement.blur();
                        } else if (previousFocus?.isConnected) {
                            previousFocus.focus({preventScroll: true});
                        }
                    });
                }, {once: true});

                openedByHover = true;
                menu.showPopover({source: button});
            });

            this.on('pointerleave', '[data-role="reactionInteraction"]', function () {
                if (!openedByHover) {
                    return;
                }
                // Allow the pointer to cross the gap between the icon and its menu.
                closeTimer = setTimeout(function () {
                    if (openedByHover && menu.matches(':popover-open')) {
                        menu.hidePopover();
                    }
                    openedByHover = false;
                }, 250);
            });

            this.on('keydown', '[data-role="reactionInteraction"]', function () {
                clearTimeout(closeTimer);
                openedByHover = false;
            });
        };
    });
}());

7 hours ago, Marc said:

The reactions is indeed an intentional change

Then i would suggest changing the hover over text from "change reaction" to "select reaction"
As there is nothing to change. The is not a "current" reaction to be "changed" with a new reaction. Except ofcouse when you already have given a reaction.

Added a report for it

Three mouse clicks for simple PM is too much. There should be message button directly on the profile.