Fixed Extending authentication modules causes XFCP errors everywhere

[Jon W]

Adding a load_class code event listener to extend an authentication module causes the extended class name (rather than the base class name) to be used for new users. This then causes the extended class to be called rather than the base class, resulting in a barrage of XFCP errors.

This makes it impossible to extend authentication modules.

The XFCP errors appear when logging in, on the contact details page and on the external authentication page, and probably other pages too.

 

[Mike]

I've worked around this with a system that can take a dynamic extension and return it to the original class name. However, you can workaround this right now by overriding getClassName().