v4.6.10-pkg-164e0029-ls35

LinuxServer Changes:

Bot Updating Templated Files

snipe-it Changes:

New in v4.6.10

This is a tiny release that fixes two bugs that would only affect a select group of users. While we hate to release multiple times in a day, we thought it prudent to get these fixes in your hot little hands as soon as possible, and we only just uncovered and fixed one of these bugs right after the 4.6.9 release went out.

The first issue would only happen for users who have full multiple company support enabled, and are not logged in as a superadmin. In that case, searching in the asset select list (for example, when checking a license out to an asset) would return an error that looks like Integrity constraint violation: 1052 Column 'company_id' in where clause is ambiguous.

The second issue affected only the /api/v1/hardware/byserial API endpoint, where we were applying the incorrect permission, so users that were NOT superadmins would get a permissions error.

Fixed

• Fixed #6367 - pass table name and column_id to scopeCompanyables()
• Fixed #6704 - don’t apply gate to $arrays collection, just check that the user can view assets

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.

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 major release. There may be a few small bug fix releases before Snipe-IT v5, but you should start preparing now.

Known Issues

Snipe-IT v4.x is not compatible with PHP 7.3. You'll need to use a version of PHP between 5.6.4 and 7.2.x. This is due to a limitation of the underlying framework. The upcoming v5 will support 7.3+.

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.

v4.6.9-pkg-164e0029-ls35

LinuxServer Changes:

Bot Updating Templated Files

snipe-it Changes:

New in v4.6.9

This is a minor bugfix release that addresses a few small API issues, and a few issues affecting user management.

For the API, we now return a 200 error instead of a 404 error when you search for an asset using the byTag() endpoint, which makes it consistent with the rest of the API. Additionally, if you send blank values to the asset update endpoint, those values will now be correctly nulled. (Previously they would not be, and the original value would be unchanged.)

For the web UI, we fixed a bug where if a location a user was the manager of was deleted, the user could not be deleted. We now no longer count deleted locations against that user deletion eligibility check. And finally, we fixed a bug where a user that previously had permissions groups assigned could not be removed from all groups. (You could control+click to deselect it, but the deselection would not be honored on save.)

API: Fixed

• Fixed #6633 - return 200 (was 404) status code on asset by tag endpoint [BREAKING]
• Fixed #6113 - use $asset->fill() vs filled() to allow blanking values via API
• User notes field is now editable via API

Web UI: Fixed

• Do not count deleted locations in managedLocations() check on user delete
• Fixed #6061 - Allow the deselection of all user groups on user edit

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.

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 major release. There may be a few small bug fix releases before Snipe-IT v5, but you should start preparing now.

Known Issues

Snipe-IT v4.x is not compatible with PHP 7.3. You'll need to use a version of PHP between 5.6.4 and 7.2.x. This is due to a limitation of the underlying framework. The upcoming v5 will support 7.3+.

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.

v4.6.8-pkg-164e0029-ls34

LinuxServer Changes:

Bot Updating Package Versions

snipe-it Changes:

New in v4.6.8

This is a minor bugfix release that addresses a few small maintenance display bugs, and a few other small issues. We've also ported embedded images in email back from the upcoming v5 branch.

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 major release. There may be a few small bug fix releases before Snipe-IT v5, but you should start preparing now.

Fixed

• Fixed problem with import when using snipeit:import command (#6550)
• Fixed saving of REMOTE_USER setting broken by 1a64879 (#6565)
• Updating LDAP such that each user is not required to be bindable
• Fixed undefined error when maintenance is associated with a deleted asset
• Only try to return the asset tag link if a valid asset id has been passed
• Specify table name in deleted user display to prevent integrity constraint error when sorting
• Fixed incorrect group route triggered when trying to access a group that's been deleted
• Fixed #6644 - asset name not linked in Reports > Asset Maintenance Report

Improved

• Switch LDAP error to debug, to avoid crapping up the logs
• Embed images in emails (ported to v5 already)
• Added calibration as a maintenance type

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

Snipe-IT v4.x is not compatible with PHP 7.3. You'll need to use a version of PHP between 5.6.4 and 7.2.x. This is due to a limitation of the underlying framework. The upcoming v5 will support 7.3+.

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.

v4.6.8-pkg-d09603b4-ls33

LinuxServer Changes:

Bot Updating Package Versions

snipe-it Changes:

New in v4.6.8

This is a minor bugfix release that addresses a few small maintenance display bugs, and a few other small issues. We've also ported embedded images in email back from the upcoming v5 branch.

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 major release. There may be a few small bug fix releases before Snipe-IT v5, but you should start preparing now.

Fixed

• Fixed problem with import when using snipeit:import command (#6550)
• Fixed saving of REMOTE_USER setting broken by 1a64879 (#6565)
• Updating LDAP such that each user is not required to be bindable
• Fixed undefined error when maintenance is associated with a deleted asset
• Only try to return the asset tag link if a valid asset id has been passed
• Specify table name in deleted user display to prevent integrity constraint error when sorting
• Fixed incorrect group route triggered when trying to access a group that's been deleted
• Fixed #6644 - asset name not linked in Reports > Asset Maintenance Report

Improved

• Switch LDAP error to debug, to avoid crapping up the logs
• Embed images in emails (ported to v5 already)
• Added calibration as a maintenance type

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

Snipe-IT v4.x is not compatible with PHP 7.3. You'll need to use a version of PHP between 5.6.4 and 7.2.x. This is due to a limitation of the underlying framework. The upcoming v5 will support 7.3+.

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.

v4.6.8-pkg-5f49d692-ls32

LinuxServer Changes:

Bot Updating Package Versions

snipe-it Changes:

New in v4.6.8

This is a minor bugfix release that addresses a few small maintenance display bugs, and a few other small issues. We've also ported embedded images in email back from the upcoming v5 branch.

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 major release. There may be a few small bug fix releases before Snipe-IT v5, but you should start preparing now.

Fixed

• Fixed problem with import when using snipeit:import command (#6550)
• Fixed saving of REMOTE_USER setting broken by 1a64879 (#6565)
• Updating LDAP such that each user is not required to be bindable
• Fixed undefined error when maintenance is associated with a deleted asset
• Only try to return the asset tag link if a valid asset id has been passed
• Specify table name in deleted user display to prevent integrity constraint error when sorting
• Fixed incorrect group route triggered when trying to access a group that's been deleted
• Fixed #6644 - asset name not linked in Reports > Asset Maintenance Report

Improved

• Switch LDAP error to debug, to avoid crapping up the logs
• Embed images in emails (ported to v5 already)
• Added calibration as a maintenance type

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

Snipe-IT v4.x is not compatible with PHP 7.3. You'll need to use a version of PHP between 5.6.4 and 7.2.x. This is due to a limitation of the underlying framework. The upcoming v5 will support 7.3+.

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.

v4.6.7-pkg-5f49d692-ls32

LinuxServer Changes:

Bot Updating Package Versions

snipe-it Changes:

New in v4.6.7

This is a minor bugfix release that fixes a compatibility issue with PHP 7.3, handles an issue with escaping values in custom report, and addresses some importer issues.

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 major release. There may be a few small bug fix releases before Snipe-IT v5, but you should start preparing now.

Fixed

• Added company info to asset maintenances transforrmer
• Fixed #6375 - lowercase keys on findAndBindUser to address LDAP syncing issue
• Fixed #6386 - licenses not searching on category name
• Fix manager id if no manager is given in importer
• Fixed department id on asset import with users
• Sets activated to 0 in UserImporter if the activated column isn’t set
• Fixed #6491, #6551, #6547, #6522 - cleaner return methods for PHP 7.3 compact()

Improved

• Improve Memcached settings (#6485)

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

Snipe-IT v4.x is not compatible with PHP 7.3. You'll need to use a version of PHP between 5.6.4 and 7.2.x.

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.

v4.6.7-pkg-8d0615e7-ls31

LinuxServer Changes:

Bot Updating Package Versions

snipe-it Changes:

New in v4.6.7

This is a minor bugfix release that fixes a compatibility issue with PHP 7.3, handles an issue with escaping values in custom report, and addresses some importer issues.

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 major release. There may be a few small bug fix releases before Snipe-IT v5, but you should start preparing now.

Fixed

• Added company info to asset maintenances transforrmer
• Fixed #6375 - lowercase keys on findAndBindUser to address LDAP syncing issue
• Fixed #6386 - licenses not searching on category name
• Fix manager id if no manager is given in importer
• Fixed department id on asset import with users
• Sets activated to 0 in UserImporter if the activated column isn’t set
• Fixed #6491, #6551, #6547, #6522 - cleaner return methods for PHP 7.3 compact()

Improved

• Improve Memcached settings (#6485)

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.

v4.6.7-pkg-89e5e7d7-ls30

LinuxServer Changes:

Bot Updating Package Versions

snipe-it Changes:

New in v4.6.7

This is a minor bugfix release that fixes a compatibility issue with PHP 7.3, handles an issue with escaping values in custom report, and addresses some importer issues.

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 major release. There may be a few small bug fix releases before Snipe-IT v5, but you should start preparing now.

Fixed

• Added company info to asset maintenances transforrmer
• Fixed #6375 - lowercase keys on findAndBindUser to address LDAP syncing issue
• Fixed #6386 - licenses not searching on category name
• Fix manager id if no manager is given in importer
• Fixed department id on asset import with users
• Sets activated to 0 in UserImporter if the activated column isn’t set
• Fixed #6491, #6551, #6547, #6522 - cleaner return methods for PHP 7.3 compact()

Improved

• Improve Memcached settings (#6485)

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.

v4.6.7-pkg-2fe9c384-ls29

LinuxServer Changes:

Bot Updating Package Versions

snipe-it Changes:

New in v4.6.7

This is a minor bugfix release that fixes a compatibility issue with PHP 7.3, handles an issue with escaping values in custom report, and addresses some importer issues.

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 major release. There may be a few small bug fix releases before Snipe-IT v5, but you should start preparing now.

Fixed

• Added company info to asset maintenances transforrmer
• Fixed #6375 - lowercase keys on findAndBindUser to address LDAP syncing issue
• Fixed #6386 - licenses not searching on category name
• Fix manager id if no manager is given in importer
• Fixed department id on asset import with users
• Sets activated to 0 in UserImporter if the activated column isn’t set
• Fixed #6491, #6551, #6547, #6522 - cleaner return methods for PHP 7.3 compact()

Improved

• Improve Memcached settings (#6485)

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.

v4.6.6-pkg-11c2d63d-ls28

LinuxServer Changes:

Bot Updating Package Versions

snipe-it Changes:

New in v4.6.6

This is a minor bugfix release that fixes a few UI issues, image upload on asset creation, and a few importer issues.

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 major release. There may be a few small bug fix releases before Snipe-IT v5, but you should start preparing now.

Fixed

• Fixed issue where admin users could accidentally disable activation when editing their own user
• Fixed double word typo in README (#6292)
• Fixed statuslabels assets() API gate so users that can see assets can view asset listings by status label
• Fixed image not uploading on asset create
• Fixed expiring assets email not sending (#6321)
• Fixed #6323 - typo in link for low inventory
• Fixed #6349 - add view permission for print all assigned

Added

• Added #6277 - manager and dept to importer
• Added #6291 - send-welcome argument in cli importer
• Allow 0 as a consumable minimum amount (Previously only allowed blank/null value)
• Added activation column in importer (accepts yes/no, or true/false)
• Added default null values if manager_id or department_id is not in the user array on import

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.