- Craft 4.0 support
- Tokens can no longer be looked up using a raw provider since it does not contain a valid identifier
- Do not attempt to save tokens to project config when in read-only mode. Issue #7
- Replaced legacy project config key values that were not properly changed before.
- Merged in settings update provided by PR #6. Thanks Mark.
- Admins were unable to create a new token via the admin panel when admin changes are not allowed.
- Removed button / forms when admin changes are not allowed
patronProviders
project config key is now saved under 'plugins.patron.providers'. When upgrading, manually moving this key is recommended.patronTokens
project config key is now saved under 'plugins.patron.tokens'. When upgrading, manually moving this key is recommended.- Tokens can be saved even if saving to project config is disabled.
- Check if columns already exist prior to adding them via migration.
- Error setting project config event on Craft before v3.1.20
- Check if columns already exist prior to adding them via migration.
- Updated dependencies and moved class structures
- Migration issue when multiple providers exist.
- Provider instances. A provider can have more than one configuration (think dev/uat/prod).
- Provider locking. A third party plugin can lock a provider from accidentally getting deleted.
- Settings::$encryptStorageData which encrypts the Provider's Client Secret (enabled by default).
- Table alias was not set on Active Query. Ref: Issue 2
- Migrations were not included on fresh install.
- Providers and tokens can be associate to an 'environment' for better multi-environment support.
flipbox\patron\events\PersistToken
event is triggered before and after storing a new token.- testing framework and docs framework
- Provider switching was calling the wrong endpoint
flipbox\patron\services\ManageTokens::find()
will find a token based on another AccessToken
- Bugs when attempting to get a token from an
AbstractProvider
Initial release.