LinuxServer Changes:
updating build logic to support branches and fixing bad variable
snipe-it Changes:
New in v4.6.5
This release fixes a few bugs that will impact all users. Primarily it fixes an issue where the activated checkbox was not pre-checked when editing a user, which could potentially cause that user to be deactivated, and also fixes a sorting bug in the assets view when sorting by model.
For the API users, the item counts on location and manufacturer are now reporting correctly.
We also fixed an LDAP issue that only impacted users whose LDAP OU contained non-user (resource) accounts which would result in a crash on LDAP sync, and a regression that was introduced in 4.3.0 which made using comma-separated alert recipient lists fail on sending.
IMPORTANT: This will be one of the final releases of Snipe-IT that will work with PHP5. Future versions of Snipe-IT will require PHP 7.1.3 or greater. Please start upgrading your versions of PHP to 7.1.3 to prepare for the next release. There may be a few small bug fix releases before Snipe-IT v5, but you should start preparing now.
Fixed
- Fixed Not unique table/alias: 'models' on custom report triggered when category is selected
- Fixed #5630 - missing directories in public/uploads which could cause errors when uploading images to components and other items
- Fixed counts to location show() API method
- Fixed regression #5965 - multiple email recipients no longer working
- Fixed #4151 - Undefined index: samaccountname on LDAP import
- Fixed #6252 - activated flag not checked when editing active user
- Fixed PHP warning
Undefined offset: 1 in upgrade.phpwhen no branch name was passed
Added
- Added
manager_idto fillable for locations API - Added group support for user API
- Added Icelandic and Serbian locales
Improved
- Removed old isActive model (unused)
Upgrading
For general upgrading instructions, click here. Users who installed Snipe-IT via Git (recommended) can just run php upgrade.php.
For a full list of changes, see the changelog.
Known Issues
Users running MariaDB 10.2.7 and later may have an issue upgrading or installing, due to a change in the way MariaDB stores null defaults. This issue will be fixed once the open pull request in the Doctrine repo is merged and a new version of Doctrine is released with these fixes. You can read more about that issue here.
After completing the upgrade process below, be sure to clear your browser cookies.
Upgrading from v3
Please see the upgrade instructions here.