Snipe-IT v5.0.7 Released

Happy Tuesday, everyone! This is a bug fix release that should handle a bunch of smaller UI bugs, and will hopefully help with some LDAP quirkiness you’ve all been kind enough to document and report for us.

Note: We did miss updating version.php to reflect that this is from the master branch, so it may be confusing to see developinstead of master in your Snipe-IT footer, but this release is definitely based off the master branch. It seemed like it would be more confusing to delete/edit the tag after it was already pushed.

Fixed

• Fixed [ch15347] – added status in Depreciation Report
• Fixed [ch9336] – Removed time in Depreciation report (it’s a date, not a datetime field)
• Fixed #8448 – “undefined” when testing email from quickstart
• Throw an error if the asset cannot be updated in the merge-users script (possible when assets fail validation on save due to serial uniqueness constraint, etc)
• Add ability to checkout an asset if the user it’s assigned_to isn’t valid. This would only happen if a merge-users went wonky
• Make last_checkout and expected_checkin fillable for API calls
• Fixed css to the bootstrap popovers for all dark mode skins (#8714)
• Exclude blank LDAP attributes
• Fixed markdown in expiring licenses alert
• Fixed #8726 – disallow archived assets to be checked out
• Enable translations of checkin notifications (#8235) and accepted assets page (#8237)
• Switch to use same convention for file names on licenses as we do on assets
• Fixed #8715 – wrong API url for unaccepted assets
• Fixed offset issue for #8732
• Fixed #8669 – Allow application/xml in SAML upload in Safari
• Updated Laravel version in README
• Added S3 url into CSP
• Fixes for #8732 – Flysystem paths, S3 migrator script
• Fixed #8733 – typo in unaccepted assets report
• Fixed #8609 – custom fieldsets not draggable anymore (regression)
• Fixed #8544 – escaping on maintenance notes
• Fixed #8737 – incorrect validation string for components qty update
• Fixed #8746 – missing comma in a translation file (#8756)
• Re-add LDAP “test login” feature to LDAP settings (helps with #8751 and #8757)
• Fixed #7850 – allow .xlsx file in upload. (#8386)
• Fixed Spanish translations duplicate string
• Fixed #8482 – Ubuntu version (#8598)
• Removed duplicate date from date macro
• Attempt to solve LDAP sync overriding administrator choices (Fixes: #8734, #8670, and #8617) #8742

Added

• Added Checkout Date Time to Asset Details Page [ch1418]
• Updated most recent translations
• Experimental script to find mismatched IDs based on logs
• Added more detail and dryrun to assigned_to vs log checker script
• Added artisan command to purge logins
• Added link to bricelabelle/snipe-it-bulkedit
• Fixed #8647 – Added additional help info on importer page

Improvements

• Moved a few of the user edit fields to make more sense (optional stuff further down)
• Added clarity in language as to what the activated flag does on LDAP screens
• Improved 2FA reset layout
• Improved upgrade.php script to check for PHP extensions (#8712)

⚠️ IMPORTANT: This release requires PHP 7.2.0 or greater. ⚠️

Upgrading

If your minimum password setting in Admin > Settings was previously less than 8, you should change this to 8 or greater before upgrading. Failure to update this may cause other settings to fail on saving.

If you’re running into an issue with images not showing up, that’s due to an outdated version of upgrade.php (outdated because of us, not you.) That script unfortunately tries (tried) to move your files to the Laravel-approved storage directory. Since that was last updated, we decided not to use that file path, so if you upgraded using upgrade.php and your images are coming up broken, please move the files in app/storage/uploads back to public/uploads and remove the symlink the upgrader created for you. (After v5.0.0, the upgrader was patched to not move those files anymore, so if you skipped the v5.0.0 upgrade you should be fine and no action is needed.)

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.

After completing the upgrade process, be sure to clear your browser cookies.

Upgrading from v3

Please see the upgrade instructions here.