Releases: DirectoryTree/LdapRecord
Releases · DirectoryTree/LdapRecord
v1.10.1
v1.10.0
Changed
Fixed
- Determine related models irrespective of the object class ordering of search results - #178 - f00d925
- Updated relation bypass exceptions for OpenLDAP support - #180 - 963581b
- Accessors not working with
$model->getFirstAttribute()
- #182 - 8f392f0 - Properly determine attribute existence when attribute is
null
- #183 - 983f5f1 - Avoid retrieving mutated attribute in
hasAttribute()
method - #189 - 7c57ed2 - Update models name in
$original
attributes upon a$model->rename()
#190 - e24ca23...8f8829c
Added
ExchangeServer
andExchangeDatabase
Active Directory models - #177 - bcc1a1c...51f9f9f, 5424fde...d99a872- Ability to create an associative array with
DistinguishedName
objects - dedd6ef
v1.9.0
Fixed
- Detaching from large groups exceeding 2000+ members
- Detaching all from a group now properly excludes primary groups
Added
- Ability to create local model query scopes by defining a method prefixed with
scope
, i.e.scopeExhangeUsers
- a652a85 User::whereHasMailbox()
query scope - Thanks to @grantholle - 1e281c2$relation->contains()
method to determine if a relationship contains a model, distinguished name or common name i.e.$user->groups()->contains('Accounting')
. You may also pass an array of any combination of the above to determine if the relation contains any of the given.
Changed
- The
$relation->exists()
method can now accept a distinguished name and common name, where it previously only accepted aModel
instance. You may now also pass an array of any combination of the above to determine if the relation contains all of the given.
v1.8.2
Fixed
- Accidental breaking change with
finally
call intry/catch
block
v1.8.1
v1.8.0
Added
- Primary groups will now be included with AD
Computer
groups relation results - e0d081c DetailedError
's are now accessible on all LdapRecord exceptions - 3216211- Several exceptions have been added to catch different causes of LDAP modification failures, providing an easier debugging experience:
LdapRecord\Exceptions\AlreadyExistsException
LdapRecord\Exceptions\InsufficientAccessException
LdapRecord\Exceptions\ConstraintViolationException
- 60d3b23
Fixed
- Relations not returning proper model instances with alternate casing defined in their respective models
$objectClasses
property - Reset integers (
-1
,0
) can now be properly set on model attributes, such aspwdlastset