- Posts: 27
- Thank you received: 0
Select room issue
- ffneil@comcast.net
- Topic Author
- Offline
- User
-
Less
More
2 years 5 months ago #791
by ffneil@comcast.net
Select room issue was created by ffneil@comcast.net
I am thinking this started after updating to the latest version of MyServer. When I select a room I get the following error14/02/2024 19:10:09.10 · DEBUG · Server.doCommand - activate-room.activate-room.masterbr from moonlightdev-fx-fm4j14/02/2024 19:10:09.10 · WARN · Server.doCommand - Unknown command activate-room.activate-room.masterbr
Please Log in to join the conversation.
- davep
- Offline
- Admin
-
Less
More
- Posts: 367
- Thank you received: 96
2 years 5 months ago #795
by davep
Replied by davep on topic Select room issue
Look in the Macros page. There is no macro by that name. That's the error you see. Change the room to call the correct activation macro.
Please Log in to join the conversation.
- ffneil@comcast.net
- Topic Author
- Offline
- User
-
Less
More
- Posts: 27
- Thank you received: 0
2 years 5 months ago #801
by ffneil@comcast.net
Replied by ffneil@comcast.net on topic Select room issue
Agree, If I change the macro name to activate-room.activate-room.masterbr it works. The button was working with activate-room.masterbr earlier in the day,
Please Log in to join the conversation.
- David Li
- Offline
- Admin
-
Less
More
- Posts: 1019
- Thank you received: 99
2 years 5 months ago #1073
by David Li
So, if the behaviour changed, then you changed something to make it change.
That's important so you can troubleshoot...ie: what did I change since then?
Open the macro that is firing (you can see which in event viewer) and then open that and see what it is doing (or trying to do).
Replied by David Li on topic Select room issue
Nothing is random (unless you intentionally make something random in a macro).Agree, If I change the macro name to activate-room.activate-room.masterbr it works. The button was working with activate-room.masterbr earlier in the day,
So, if the behaviour changed, then you changed something to make it change.
That's important so you can troubleshoot...ie: what did I change since then?
Open the macro that is firing (you can see which in event viewer) and then open that and see what it is doing (or trying to do).
Please Log in to join the conversation.
Time to create page: 0.172 seconds