[021] XenForo WebSockets 2.1.4

• Fix: In some browser states, AppStateManager was incorrectly checking DOM readiness, which could lead to JS errors on XenForo 2.3

• Fix: (XenForo 2.3) Third-party jQuery inclusion could break the event system.

• Fix: window.ws.event.on does not work correctly on XenForo 2.3
• Fix: X-WebSockets-Page-Uid header not passed to AJAX requests on XenForo 2.3

• This update is supposed to fix an annoying bug that has existed since the add-on release: incorrect display of online users in expansions such as Real-Time Chat and XenForo Messenger
• Implemented an elegant solution for updating the csrf token and connecting to the websocket server when restoring a page from the back-forward cache: this should improve the connection when restoring a tab in a browser on mobile devices and help avoid the "Security error..." error.
• XenForo 2.3 support
• Name pattern feature for channels
• XF.Echo and XF.EchoManager now are deprecated, use window.ws.echo and window.ws.manager instead
• Updated soketi config parameters generation format to more user-friendly
• Removed some permission checks in the broadcast controller to ensure websockets work correctly in different situations
• Minimum PHP version now is 8.1

On forums with closed access for guests, certain scenarios required a websocket connection, but this did not occur due to viewing permissions check

Fixed​

• The Pusher Host option was not passed to the frontend

• Prevented error output on the user side in case of problems with the websocket server

Fixed:
In some cases, the channel name could be parsed incorrectl

• Removed check for installed soketi on the server when installing daemons
• Added /bin/bash prefix to avoid "Executable path is not absolute, ignoring" error

NA