The logic for storing active users has been changed. Previously, I made a mistake and users were identified on the Swoole server by user_id. This caused problems. For example, when a user had a page open in the browser and then opened it from another device, the data would be overwritten, and when the user closed the page on any device, they were completely disconnected from the socket. As a result, they no longer received events in the browser.
Security has been improved. All communications with the Swoole server (http and websocket protocols) now require validation of a special token.
Code refactoring.
Before updating, stop the Swoole server, as the mechanism for managing the socket server from the Xenforo admin panel has been changed.
Fixed a bug that occurred when visiting the plugin settings page in the Xenforo admin panel when the socket server was run from the console instead of the admin panel.
Those who have encountered this error should stop the socket server after the update, kill processes listening on the socket server port and start the socket server again.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.