Web admin bug: Login extensions

[ritty]

OK, so I spent several hours trying to get a Login Event Handler extension working. I kept setting it up, trying it, and would get an extension not found error. Delete the extension, try some code changes, set it up, extension not found error. Repeat.

I finally noticed a real small thing on the LoginEventHandler wiki page. The image shows Plugin Type: Login Event Handler.

When I was setting it up, the Plugin Type always said server level plugin. There was no way for me to change this.

The only way I could get the web admin to say Plugin Type: Login Event Handler was to delete all my other extensions. Set up the login extension, and then set it up. At this point, the plugin type showed Login Event Handler and all worked fine. I then had to reinstall all my other extensions.

Definitely an annoying bug.

Version: Windows, 4.0.6

[tcarr]

Does your login event handler extend BasePlugin or does it extend BaseLoginEventHandler? And is it in the login event handler section of your Extension.xml? Because I've never had a problem like this, and I use both in the same extension, and I'm running ES4.0.6 now.

[ritty]

The handler extends BaseLoginEventHandler. It is in the event handler section of extension.xml.



<Extension>
<Name>Login</Name>
<EventHandlers>
<LoginHandlers>
<LoginHandler>
Login
Java
Login</Path>
</LoginHandler>
</LoginHandlers>
</EventHandlers>
</Extension>


public class Login extends BaseLoginEventHandler {
.
.
.
}

It works perfectly fine if this is the only extension installed or is set up before any other extension.

The problem appears when there are already installed extensions, for example our games' extensions, and we then try to add the login extension as a completely separate extension to be utilized by all our games.

I'd be happy to Crossloop this with you or create a screen capture video if I am not able to describe this so that it makes sense.

[tcarr]

Ah... the way I do it always has the login event handler as part of the extension. I normally put all my games into the same extension. I do have multiple extensions running on the same ES4, for different projects.

Perhaps Mike has some ideas.

[ritty]

I tried it this evening with everything in one extension. Seems to work OK. So the bug is definitely with two or more extensions.