v4.1.0

Changes since v4.0.0-RC3:

• Stop tracking IDE files (.idea folder) 97cae84
• DatePicker and SortableBehaviour CakePHP 4 fixes (#29)
• Only add password hash to last_passwords when password has changed 938cbf6
• Make fa(l/r) icon style customizable in CkToolsHelper via new config iconStyle 3e85155
• Make icons customizable in CkToolsHelper. See CkToolsHelperTest for usage examples e3e971e
• Restore possibility to overwrite icons in CkToolsHelper without prepending the "fa-" 8e0185a
• Fix disabling icons all together in all CkToolsHelper button functions 1841117
• Add a target to return the HTML string instead of PDF content in PdfGenerator (#30)

Also, first stable v4 version 🎉

v3.1.7

Fixes critical bug where default date contents are overwritten with date of today, which also did not reflect properly in the user facing input field

v3.1.6

• Update DatePicker selects on init (#27)

Prevents the visible datepicker input to be filled but the hidden ones sent to the server being empty, potentially resulting in confusing validation errors

v3.1.5

To disable specific days of the week in the Datepicker component, set the days of week to be disabled from the controller action to the FrontendBridge under the key daysOfWeekDisabled.
Values are 0 (Sunday) to 6 (Saturday). Multiple values should be comma-separated. Example: disable weekends: [0,6]

As code in the controller action:

$this->FrontendBridge->setJson(['daysOfWeekDisabled' => [0, 6]]);

v4.0.0-RC2

v4.0.0-RC3

Fix locales path

v4.0.0-RC2

Update constraint versions

CakePHP 4.0 compatibility

v4.0.0-RC1

Fix and add unit tests

• Prefixed every fixture with "CkTest", because if you have a project with a users table and fixtures (very common) this package and any plugin having unit/integration tests that are executed after the tests of this package produced conflicts.
  That's because the users table is not changed back to the fixture/schema of the main app after the tests of this package and therefor potentially missing some fields that are only present in the users table of the main app.
  To easily prevent this, I addded the "CkTest" prefix to every fixture this package uses, minimalizing the potential of naming conflicts with real apps.
• Added unit tests for the latest configuration value of the StrictPasswordBehavior: "minUserNameLength", which sets a lower limit for the length of name fields of the user to be considered when checking that the password does not contain any of the names. This prevents people with very short names getting totally random passwords rejected because their short name appears in the random characters of their desired new password

v3.1.3

Translations updated in previous release were not reflected in the binary .mo files, which is now rectified

v3.1.2

• make the minimum length of first- and lastname where their occurrence in the password will trigger a validation error configurable. This was necessary due to the fact that a name with one or two characters could easily invalidate any random password
• fix validation error message translation