Server-side plugin stopped working after installing ES 3.6

[crusader]

Hello everyone.

I'm having trouble with a flash room plugin.

As soon as I installed ES 3.6, it stopped working.
Actually, it runs and does not produce any error, but the line which
sends a message back to the client does not work:




returnToUser ("EveryonesDetails", data, user);

function returnToUser (action, object, user) {
server.sendMessage("private", [user], action, object);
}


I haven't changed anything in the code and this is really bugging me.
I'm sure the code reaches the returnToUser function, because I used
a trace.

Any ideas?

Thanks

[crusader]

I just found out what happens!

This is the code that receives the pluggin message:



function pluginMessageReceived(plugin, action, variables, possibleNewParameter) {
trace("plugin:"+plugin);
trace("action:"+action);
trace("variables:"+variables);
trace("possibleNewParameter:"+possibleNewParameter);
...
...
...
}
es.pluginMessageReceived = pluginMessageReceived;


In the Output dialogue, I get:

plugin:giannis71
action:EveryonesDetails
variables:[object Object]
possibleNewParameter:undefined


I think some change was made at the way the server handles the plugins and instead off passing the Plugin Name as a parameter
the function:



server.sendMessage("private", [user], action, object);


sends the variable "user".

Jobe, I think you should look into that.

[crusader]

I forgot to say, I added the possibleNewParameter to see if maybe the new version of the plugin return the parameters in a different order or something.
Of course, the variable came out as undefined, so that's not the case, there is for sure an error in the server.sendMessage method.

[jobem]

Hi crus,

It appears that you are correct. I just tested and verified that...very odd that it used to say the plug-in name and now it says the user's name. I'll report it to Mike ASAP.

FYI: We were hoping to release 3.65 really soon, maybe this weekend or early next week. It will have a few fixes plus some other stuff. I'm sorry for the issue. I hate to suggest a work around, but if you absolutely need one you can pass the name of the plug-in as a variable with each move.

Sorry again,

[crusader]

Ok Jobe, thank you.

Believe me, I know how thinks like that can come up when trying to release a new version of something!
I hope you are going to fix this ASAP, because both my Lobby and my Game do not function!

I'm going to bypass the PluginName checking for now since I only use one Plugin at the time and I
really need to go on with the development of this project.

Thanks.

[jobem]

Hi crus,

Mike is actually working on the fixes as we speak.