- Error when repopulating a user index after dissociating a user from an org
- Error when dissociating a user from an organization
- Element index cache is removed when a user is dissociated from an organization
- Query with relations not handling the value 'false' correctly.
- Various PHP 8 typing issues
- PSR-4 autoloading issue w/ Composer v2 #18
- Addressed minor issues w/ 3.4 styling
- Access to the organization type switcher can be made via
window.OrganizationTypeSwitcher
- Project config is referencing the entire field layout instead of just the field layout id.
- UserAssociation query can be filtered by user type.
- Relaxing explicit '!==' id checks to '!='.
- Migration typo in class name
- Refactored getters and setters used to access/manage relationships directly from
Organization
andUser
elements. As a result,Organization::getUsers()
,Organization::getTypes()
,User::getOrganizations()
andUser::getUserTypes()
return aRelationshipInterface
which is used to access and manage relationships.
- Craft Project config support.
- Associations can bypass child association saving
- Validation issue when checking a newly created organization that has been associated to a user
- Ability to disable sort order enforcement for organization/user associations.
- Many-to-many relationships have a 'manager' class attached to the object where 'relational' logic resides
- CP organization user list management enhancements
- Various methods used to access/manage relationships directly from
Organization
andUser
elements. Organization::getUsers()
,Organization::getTypes()
,User::getOrganizations()
andUser::getUserTypes()
now return aCollection
(not a query).- It is no longer recommended to
Query::setCachedResults()
in order to set new relations, use the relationship manager
- Removing all user types would result in a Postgres query error #17
- When passing 'false' to query params, throw an exception to halt query execution #13
- Ordering of associated users by title would result in a query error.
- User State filters to applicable queries
- Scenarios when saving a user would delete all their associated organizations.
- UserAssociation asset bundle was restored after accidentally being removed.
- Managing organization user roles has moved to an element action.
- Added a 'state' to Organization Users
- Query params are prepared in a more simple and direct way
- Gracefully handle looking up a record by the unique handle or id.
- Passing an element to Organization::findOne() will check and return the element
- GA release
- Reset query relations table joins on new execution of query.
- Rare instance when multiple of the same relations could be added to a User Query
- User type association HUD is grouped by source headings
- Sidebar navigation to easily get to/from settings and elements
- Organization Type field type can customize the drop down first option
- User's organization list should appear even if no organizations are present.
- User detail sidebar can add/remove organizations.
- User detail sidebar lists the organizations that a user is associated to.
- Bug when saving a user association another association may get deleted.
- Issue where saving a new organization without a type associated would throw and exception.
- Issue where 'organizationId' and or 'userId' were not getting applied properly to user association queries.
- The concept of state from elements per #4.
- User Type associations were not saving correctly when all associations were un-selected.
- Intro to unit tests
- Services have a configurable cache duration and dependency that can be set via the plugin's settings config.
- OrganizationQuery no longer automatically adds 'types' as an eager loading key
- Error when passed attempting to set types on an organization with a null value
- Removing user from organization was causing an error
- Organization type urls on listing page and handle slug on detail page
- Reference to legacy sort order property
- Typo in migration file renaming which prevented the migration from running
- User associations can be sorted by user and organization.
- Organization Type single select field type
- Element and Query behaviors were not getting set due to new Craft CMS register behaviors event.
- Default field layout was being deleted with organization type layout was selected
- Organization type field layout defaults to main default if null (instead of loading an empty layout).
- Renamed the concept of user categories to user types (not backwards compatible)
- Updated dependencies
- load more action when viewing more than associated organization users
- fixed issue where Join Date was not getting updated correctly.
- dependency templates were not registered in admin views
- Renamed plugin class to
Organizations
- Namespace is now using
organizations
instead oforganization
Initial release.