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).
-
@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.
-
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.
-
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.
@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.
--
Dustin Dauncey
www.d19.ca -
@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.
