<![CDATA[Warning: Don't update AuthLDAP plugin to 2.4.3 from 2.4.2, breaks LDAP login.]]>I had my authLDAP plugin set to auto-update in WordPress sites as a test a while back, today there was an update to it from 2.4.2 to 2.4.3. Ref: https://github.com/heiglandreas/authLdap/releases/tag/2.4.3

It was updated automatically by WordPress per the configuration I set, however logging in with LDAP credentials then failed for every site that the update occurred on.

I was thankful I could restore from backups, but that was an interesting situation since WordPress seems to auto-update within a minute of restoring from backup, so needed to go in and enable recovery mode immediately before it was auto-updated, downloaded the folder, then restarted the instance and removed authLDAP and re-uploaded from previous step. Wasn't hard at all but more than I expected. In the meantime I've disabled auto-update for authLDAP (though I'm not sure why this is needed, why the compatibility issue occurs).

]]>https://forum.cloudron.io/topic/4142/warning-don-t-update-authldap-plugin-to-2-4-3-from-2-4-2-breaks-ldap-loginRSS for NodeSat, 18 Apr 2026 19:01:05 GMTWed, 06 Jan 2021 04:48:40 GMT60<![CDATA[Reply to Warning: Don't update AuthLDAP plugin to 2.4.3 from 2.4.2, breaks LDAP login. on Thu, 07 Jan 2021 19:11:27 GMT]]>@d19dotca This should be fixed in the latest package. Thanks for reporting.

]]>https://forum.cloudron.io/post/23019https://forum.cloudron.io/post/23019Thu, 07 Jan 2021 19:11:27 GMT<![CDATA[Reply to Warning: Don't update AuthLDAP plugin to 2.4.3 from 2.4.2, breaks LDAP login. on Thu, 07 Jan 2021 19:39:29 GMT]]>There's more deep rooted issues - https://github.com/heiglandreas/authLdap/issues/194 . The package itself is wrong and unfortunately wp admin suggests it as an update. Breaking a lot of things.

]]>https://forum.cloudron.io/post/23025https://forum.cloudron.io/post/23025Thu, 07 Jan 2021 19:39:29 GMT<![CDATA[Reply to Warning: Don't update AuthLDAP plugin to 2.4.3 from 2.4.2, breaks LDAP login. on Thu, 07 Jan 2021 19:11:27 GMT]]>@d19dotca This should be fixed in the latest package. Thanks for reporting.

]]>https://forum.cloudron.io/post/23019https://forum.cloudron.io/post/23019Thu, 07 Jan 2021 19:11:27 GMT<![CDATA[Reply to Warning: Don't update AuthLDAP plugin to 2.4.3 from 2.4.2, breaks LDAP login. on Wed, 06 Jan 2021 22:31:55 GMT]]>@girish Ah okay that makes sense, because I saw after downloading and uploading the packages manually that the names were different. I think the package currently gets installed from GitHub, maybe that's an issue? If it gets installed from the WordPress Plugin Directory instead that may solve it in terms of the naming convention for the plugin. I think you're right, if the package was built with "authLdap" instead it'd have continued to work. 🙂

]]>https://forum.cloudron.io/post/22973https://forum.cloudron.io/post/22973Wed, 06 Jan 2021 22:31:55 GMT<![CDATA[Reply to Warning: Don't update AuthLDAP plugin to 2.4.3 from 2.4.2, breaks LDAP login. on Wed, 06 Jan 2021 06:38:16 GMT]]>The issue seems to be the directory of the plugin gets renamed from authLdap-2.4.2 to authldap after the update. And because of this name change looks like the plugin also gets disabled after the update. Just activating the plugin after update seems to work.

I will see if I can push a package update that renames it to authldap itself. Does anyone know how these plugin directories are named? I will investigate tomorrow.

]]>https://forum.cloudron.io/post/22922https://forum.cloudron.io/post/22922Wed, 06 Jan 2021 06:38:16 GMT