19 hours ago, My Sharona said:

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

Previously that depended in whether your device had a touch input, so it wasn't really consistent.

19 hours ago, Cedric V said:

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

I cannot reproduce this. if this is a dev/self hosted environment make sure your static/ folder is up to date (delete the contents first) with the download from the client area and clear your browser cache.

19 hours ago, Kirill Gromov said:

Why did you remove profile information from mobile devices?

Yes, we removed it because tapping on the author name now shows the profile card (inc mobile) which offers more detailed information.

19 hours ago, Cedric V said:

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

What's wrong with Notifications?

With Quotes are you referring to the known multiquote / quoting on mobile issues or something else?

13 minutes ago, Stuart said:

What's wrong with Notifications?

Notifications didn't work on Administrata. It was the result of underscore JS being taken away. It has been fixed now. With quotes I was also referring to mobile issues which lags the browser. But you are aware I've noticed.

I was a bit annoyed that the announcement post didn't include developer notes and the removal of underscore JS, Stuart. I know it wasn't your intention of course, but if that could be prioritized in the future, that'd be great. 👍

Apart from the issues, the update has been great!

5 minutes ago, Cedric V said:

Notifications didn't work on Administrata. It was the result of underscore JS being taken away. It has been fixed now. With quotes I was also referring to mobile issues which lags the browser. But you are aware I've noticed.

Thanks for clarifying that was related to customisations.

Quoting on mobile is fixed for beta 2.

8 minutes ago, Cedric V said:

I was a bit annoyed that the announcement post didn't include developer notes and the removal of underscore JS

I understand, these usually generate automatically based on labels but it doesn't look like we've used them where we should. I'll make sure we do that moving forwards.

I have removed some leftover wrapper references to underscore in beta 2, I cannot reproduce them throwing an error though.

29 minutes ago, Stuart said:

Thanks for clarifying that was related to customisations.

Quoting on mobile is fixed for beta 2.

I understand, these usually generate automatically based on labels but it doesn't look like we've used them where we should. I'll make sure we do that moving forwards.

I have removed some leftover wrapper references to underscore in beta 2, I cannot reproduce them throwing an error though.

Thanks. Well appreciated. Ignore the error, it was due to a 3rd party app.

The color palette in theme editor is not changing colors after saving.

Edited October 3Oct 3 by Drewfus

Happy to see mentions are still just a hover.

@Square Wheels

They also have a new style, not a pill any longer.

There's already a bug report open to fix that 😇

1 minute ago, Stuart said:

There's already a bug report open to fix that 😇

I am assuming 5.1.0 is running on this site.

Today, Oct 4th.

Edited October 4Oct 4 by My Sharona

I like the UI changes to reactions and profile card popup (especially on mobile where the double click for reactions were kind of janky until now).

Is there any room for further tweaking the profile card popup? When I click a username and the card appears, I think users will much prefer to have easier access to Message (and Ignore, although less important), rather than those options being tucked under an 'Options' dropdown. Conversely, "find content" might be something that would be better served in an "options" dropdown?

Thanks for the beta! It's great to see PHP 8.2–8.5 compatibility (#7603) and the PHP 8.5 member export fix (#6857) included in this release.

One question though: PHP 8.6 is scheduled for general availability on November 19, 2026, and it's already at the release candidate stage with its feature set frozen. Since 5.1.0 is still in beta and the final release may land around the same time, why not target PHP 8.6 compatibility directly in 5.1.0?

PHP 8.6 comes with a fair number of deprecations and new session defaults (HttpOnly, SameSite=Lax), so it would be reassuring to know it has been tested against the RCs before we upgrade our servers.

Is PHP 8.6 support planned for 5.1.0 final, or should we expect it in a later 5.1.x release?

Thanks!

14 hours ago, MEVi said:

Thanks for the beta! It's great to see PHP 8.2–8.5 compatibility (#7603) and the PHP 8.5 member export fix (#6857) included in this release.

One question though: PHP 8.6 is scheduled for general availability on November 19, 2026, and it's already at the release candidate stage with its feature set frozen. Since 5.1.0 is still in beta and the final release may land around the same time, why not target PHP 8.6 compatibility directly in 5.1.0?

PHP 8.6 comes with a fair number of deprecations and new session defaults (HttpOnly, SameSite=Lax), so it would be reassuring to know it has been tested against the RCs before we upgrade our servers.

Is PHP 8.6 support planned for 5.1.0 final, or should we expect it in a later 5.1.x release?

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.

On 10/3/2026 at 11:39 AM, Drewfus said:

The color palette in theme editor is not changing colors after saving.

Added a bug report for this

18 hours ago, My Sharona said:

I am assuming 5.1.0 is running on this site.

Today, Oct 4th.

I'm not able to replicate any issues with these at all. Are you still seeing this? Added bug report. Thank you.

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.

1 minute ago, bags_ppp said:

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

What's wrong with them? they're working as expected for me.

When you click on them nothing happens. Now it works here again, but not on my community:

I cleared cache in IC and Cloudflare. It does not work even with default theme. Nothing in dev console.

Edited October 9Oct 9 by bags_ppp

Im not able to replicate this at all unfortunately. What browser and browser version are you using? Also, are you using any browser plugins?

Chrome( vanilla, no single addo) and my default Firefox.

Is it maybe because of PHP 8.2?

Solve. I had this in theme editor css:

/* 30px of hover-leniency around hovered reactions */
.ipsReact_types ul::before{
	content: "";
	position: absolute;
	inset: -30px;
}

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

4 minutes ago, Moestuin said:

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.

It would be fine for mobile; I get people catch the reactions by mistake, but on desktop the old 5.0x way would be so much better.

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;
            });
        };
    });
}());