Not working in newer version?

[n-bux]

Hi, I guess the plugin is not working with newer versions (I tried v.2.3.0 – below you find the log messages)?

Do you think you can fix this?

Or does anybody have another idea how to notify all users for a given period of time, regardless if they are logged in at the moment of publishing the info or open a pad later in the time period (similar to #12 )? (@JohnMcLear , @SamTV12345)

 [WARN] settings - the `client` context property for the handleMessageSecurity and handleMessage hooks is deprecated; use the `socket` property instead 
    at Object.get client (/var/www/html/src/node/handler/PadMessageHandler.ts:347:16)
    at exports.handleMessage [as hook_fn] (/var/www/html/src/plugin_packages/.versions/ep_message_all@2.0.1/index.js:40:60)
    at <anonymous> (/var/www/html/src/static/js/pluginfw/hooks.ts:273:18)
    at new Promise (<anonymous>)
    at callHookFnAsync (/var/www/html/src/static/js/pluginfw/hooks.ts:236:16)
    at <anonymous> (/var/www/html/src/static/js/pluginfw/hooks.ts:351:54)
    at Array.map (<anonymous>)
    at Object.exports.aCallAll (/var/www/html/src/static/js/pluginfw/hooks.ts:351:13)
    at Object.exports.handleMessage (/var/www/html/src/node/handler/PadMessageHandler.ts:371:20)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async <anonymous> (/var/www/html/src/node/handler/SocketIORouter.ts:84:14)
[2025-08-13T10:17:38.295] [WARN] settings - the `client` context property for the handleMessageSecurity and handleMessage hooks is deprecated; use the `socket` property instead 
    at Object.get client (/var/www/html/src/node/handler/PadMessageHandler.ts:347:16)
    at Object.exports.handleMessage (/var/www/html/src/plugin_packages/.versions/ep_hash_auth@10.0.1/ep_hash_auth.js:159:27)
    at <anonymous> (/var/www/html/src/static/js/pluginfw/hooks.ts:273:18)
    at new Promise (<anonymous>)
    at callHookFnAsync (/var/www/html/src/static/js/pluginfw/hooks.ts:236:16)
    at <anonymous> (/var/www/html/src/static/js/pluginfw/hooks.ts:351:54)
    at Array.map (<anonymous>)
    at Object.exports.aCallAll (/var/www/html/src/static/js/pluginfw/hooks.ts:351:13)
    at Object.exports.handleMessage (/var/www/html/src/node/handler/PadMessageHandler.ts:371:20)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async <anonymous> (/var/www/html/src/node/handler/SocketIORouter.ts:84:14)

[SamTV12345]

Hi @n-bux . Did you try the develop branch of Etherpad or did you use an official release for Etherpad as your base?

[n-bux]

Hi, thanks for replying - I am using release v2.3.0

[Gared]

@n-bux Thanks for your bug report. I tried to debug the problem and then noticed that with the new admin-UI the plugin-page is not shown at all. @SamTV12345 Can you give me a hint?

[SamTV12345]

For the shout feature there is already a native way to do this in Etherpad in the admin console to all connected sessions. Does that suffice? Otherwise we can also integrate some of your changes like sending to all new connections in the next x seconds.

[Gared]

AS @n-bux mentioned this plugin also displays the message for a specific time that you can configure

Or does anybody have another idea how to notify all users for a given period of time, regardless if they are logged in at the moment of publishing the info or open a pad later in the time period (similar to #12 )?

But anyway this eejs_block is also used by other plugins that are also broken. Shouldn't this be integrated again in etherpad again?

[SamTV12345]

Then we should integrate the things. I think an admin tool can be quite elaborate and have a large native toolchain for administration.