Closed DijkeMark closed 1 year ago
Hi @DijkeMark,
To clarify this issue, you're only experiencing this with the Directory Emulator, right?
Unfortunately I have not been able to test this against an actual ActiveDirectory yet.
Thanks @DijkeMark I'm able to reproduce this, these new methods are the culprit:
Working on a patch. I should have this out by end of weekend.
New release is out with a patch for this, thanks again for the report! 🙏
https://github.com/DirectoryTree/LdapRecord-Laravel/releases/tag/v3.0.9
Thanks for the fix, everything seems to be working on my end now aswell. 👍
Environment:
Describe the bug:
I am using multiple custom classes that extend the ActiveDirectory classes in which I (among other things) set a custom connection. In the 3.0.8 update, I am no longer able to use a custom connection when using the
::find()
method on the custom classes.The
::find()
calls will simply return null, which is not true, considering I can retrieve all records using::all()
which returns all rows I expect.The same goes for using
->refresh()
which returnsTypeError: LdapRecord\Models\Model::fresh(): Return value must be of type App\Models\Ldap\User|false, null returned
See the following example:
The custom user class:
The TestCase class (which is the default TestCase class in the Test directory):
The connections in ldap.php config file