Skip to content

@snipe snipe released this Feb 22, 2019 · 13 commits to master since this release

New in v4.6.13

This release fixes a potential issue introduced in #6693, where we added the ability to nullify values via the API. It's a migration that sets several fields in the database to be nullable where they were sometimes previously not. (Fields are typically nullable by default, as we enforce those rules at the model level, however versions of Snipe-IT installed using a different version of MySQL may have had those fields created without the nullable attribute correctly set.)

In those cases, attempting to create assets, locations, users, etc with blank fields (even fields that are not required through the UI) could result in the MySQL error: Illuminate\Database\QueryException: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'foo' cannot be null.

The issue was introduced by implementing the ConvertEmptyStringsToNull() middleware, which is necessary by the API to nullify values (versus passing empty strings), but also caused issues for folks for whom those fields were not already nullable.

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.

Assets 2

@snipe snipe released this Feb 16, 2019 · 18 commits to master since this release

New in v4.6.12

This release fixes a small bug that was introduced in the last release which inadvertently changed the auto_increment_prefix to a boolean field. If you skipped the 4.6.11 release, this won't affect you, but we changed that migration in-place and then created an additional migration for folks who may have already upgraded. You may need to reset your auto increment prefix in the settings if you had upgraded to v4.6.11.

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.

Assets 2

@snipe snipe released this Feb 14, 2019 · 20 commits to master since this release

New in v4.6.11

Happy Valentines Day! To show you our love, we have a new release for you!

This release fixes a few very small bugs, one related to password confirmation validation, one related to the category not being respected in the consumables by category listing, and one more that addresses an issue where the pagination on one type of item could impact another, making it look like you have no items in that listing who you really do.

letmeloveyou

Fixed

  • Fixed #6703 - fixes password confirmation
  • Fixed #6676 - consumables API not respecting category id
  • Fixed issue where offset could be greater than total items, resulting in "No results"

Breaking API changes:

  • The password confirmation fix will require password_confirmation to be passed in API called when creating a new user, and it must match the password field.

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.

Assets 2
Pre-release

@snipe snipe released this Feb 13, 2019 · 97 commits to develop since this release

New in v5

IMPORTANT: This version of Snipe-IT requires PHP 7.1.3 or greater.

We're thrilled to announce the beta release of the long-awaited Snipe-IT v5! Lots of stuff is changed under the hood, as we've upgraded the underlying framework to Laravel 5.7, but there are tons of bugfixes and new features, as well as some UI improvements.

One of the bigger changes to the system is the introduction of Flysystem support, which means you can host your asset uploads, logos, etc on S3 or Rackspace.

screen shot 2019-02-13 at 2 23 00 am

We've also reworked a lot of the backend LDAP functionality and made the UI on the LDAP settings page a little easier to use.

The small things matter as much to us as the big ones do, so we've spent some time trying to really refine some of the commonly used UI elements, for example the improved logo upload+preview interface:

better-logo

Additionally, we've cleaned up the contextual help, and added a Save button at the top of forms that tend to run a little longer.

create_asset____snipe-it_demo-3

Plus, we have (very basic) client-side validation to help give you more immediate feedback if you've missed a required field in the forms.

But wait - there's more! Here's a full list of the changes:

Added

  • Added attempted logins admin screen
  • Added better support for NFC/RFID/Barcode scanners in select boxes
  • Added ability to trigger password reset emails for users
  • Added Raspbian 9.4 to snipeit.sh installer
  • Added Department to user import
  • Added php version check to upgrade.php
  • Added check for minimum PHP version in setup
  • Added #5957 - Flysystem support #6262 which allows you to use S3 or Rackspace to host your file uploads
  • Added accessories images for seeder
  • Better validation for manager_id on User model
  • Added save button at top of long create/edit forms
  • Added basic front-end validation
  • Added alt tags to logo
  • Added toggleDisabled on form validator
  • Better logic for disallowing company selection when user is not a superadmin and FMCS is enabled
  • Make dashboard snapshots clickable
  • Added #6349 - add view permission for print all assigned
  • Added Department update API endpoint
  • Added #6463 - ability to override session path in .env
  • Added #6464 - added company name to searchable field in user search
  • Added ability to upload favicon and email logo
  • Added #6099 - XML as new uploadable file type
  • Added #6241 - user license api endpoint
  • Added #6617: Added endpoint for licenses checked out to an asset
  • Added #6625 - include fully depreciated date in custom asset report
  • Added simplified slack channel regexp and allow private (no # prefix) channel
  • Added asset tag to asset maintenances report

Fixed

  • Fixed #6004 - set a default next_audit_date if none provided
  • Fixed #6011 - use correct file created at date
  • Limit width of title logo so it doesn’t break with long names
  • Fixed #6013 - add accessory checkout notes to detail page
  • Fixed #5964 - Group IDs can be now be passed to user creation API
  • Fixed bug where checkout right-side menu would display assets checked out to non-users with the same ID
  • Fixed DBAL issue affecting MariaDB 10.2.7 or greater
  • Fixed #6029 - Model number not appearing in checkin/checkout emails
  • Fixes #6016 - Check for an existing username before getting creative
  • Fixed - Only allow activated users to reset their password
  • Fixed - Set activated checkbox to 1 by default on new user
  • Fixed #6082 - don’t show expected checkin in email if none given
  • Fixed MAC address regex
  • Fixed: #6263 V5 - Missing oauth tables when using the setup
  • Fixed issue where admin users could disable activation when editing their own profile
  • Fixed #6323 - typo in link for low inventory
  • Allow min:0 for consumables
  • Fixed check whether the user can edit an asset before allowing them to change the name on checkout
  • Fixed #6175 - crashing when accessory has been deleted
  • Fixed #5879 - added user department filter for custom report
  • Fixed #6386 - licenses not searching on category name
  • Fixes #6341. Adding condition that checks offset of licenses seats when the user looks other page than the first.
  • Fixed: #5896 Custom fields of type "CUSTOM REGEX" are always saved as "ANY
  • Fixed #5554 - Language of acceptance email ii admin language, not recipient language
  • Fixed bad groups route on error
  • Fixed #6350 - import page was blank on MS Edge browser
  • Fixed issue importing encrypted custom fields
  • Fixed #6644 - asset name not linked in Reports > Asset Maintenance Report
  • Fixed issue where users cannot log in with generated password
  • Fixed #6634: Asset Import History fixes and optimizations
  • Fixed #6704 - byserial asset API endpoint permissions

Removed

  • Removed gh-changelog.php - we don’t use it anymore

Improved

  • Insert audited items to the top of the list in bulk audit
  • Use username instead of email address in password reset to prevent confusion

Documentation

Want to Help Test?

Awesome! First things first, you should NOT test this in production yet, as it's a beta release. If you'd like to help us test, make a new copy of Snipe-IT and upgrade your copy to v5.0.0-beta-1.0, that way your data is safe. You should treat this test instance as a version you could easily throw away when you're done testing. (Hopefully it won't come to that, but hey, computers are hard.)

Things we're very interested in folks testing:

  • LDAP/AD integration (login and sync)
  • Using S3 to store files. We've built a little tool to help you migrate your local files to S3, which you can read about here.
  • Client-side validation
  • The importer, as always - that thing's a bear

If you need to create new bug reports for this beta release, please make sure you include the beta release version in the Github issue title so we can easily see that it's an issue specific to this beta.

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.

Upgrading from v3

Please see the upgrade instructions here. After completing the upgrade below, be sure to clear your browser cookies.

Thanks!

Special thanks to @jwhulette, @patrict, @VELIKII-DIVAN, @liquidhorse, @Seldaek, @inietov, @benrubson, @NMathar, @smb, @Sxderp, @fanta8897, @andreybolonin, @shinayoshi, @reuser, @KeenRivals, @omyno, @jackka, @herroworrd, @colin-campbell, @HinchK, and @uberbrady for helping bring v5 to life!

awkward-thank-you

Assets 2
Pre-release

@snipe snipe released this Feb 13, 2019 · 207 commits to develop since this release

New in v5

IMPORTANT: This version of Snipe-IT requires PHP 7.1.3 or greater.

We're thrilled to announce the beta release of the long-awaited Snipe-IT v5! Lots of stuff is changed under the hood, as we've upgraded the underlying framework to Laravel 5.7, but there are tons of bugfixes and new features, as well as some UI improvements.

One of the bigger changes to the system is the introduction of Flysystem support, which means you can host your asset uploads, logos, etc on S3 or Rackspace.

screen shot 2019-02-13 at 2 23 00 am

We've also reworked a lot of the backend LDAP functionality and made the UI on the LDAP settings page a little easier to use.

The small things matter as much to us as the big ones do, so we've spent some time trying to really refine some of the commonly used UI elements, for example the improved logo upload+preview interface:

better-logo

Additionally, we've cleaned up the contextual help, and added a Save button at the top of forms that tend to run a little longer.

create_asset____snipe-it_demo-3

Plus, we have (very basic) client-side validation to help give you more immediate feedback if you've missed a required field in the forms.

But wait - there's more! Here's a full list of the changes:

Added

  • Added attempted logins admin screen
  • Added better support for NFC/RFID/Barcode scanners in select boxes
  • Added ability to trigger password reset emails for users
  • Added Raspbian 9.4 to snipeit.sh installer
  • Added Department to user import
  • Added php version check to upgrade.php
  • Added check for minimum PHP version in setup
  • Added #5957 - Flysystem support #6262 which allows you to use S3 or Rackspace to host your file uploads
  • Added accessories images for seeder
  • Better validation for manager_id on User model
  • Added save button at top of long create/edit forms
  • Added basic front-end validation
  • Added alt tags to logo
  • Added toggleDisabled on form validator
  • Better logic for disallowing company selection when user is not a superadmin and FMCS is enabled
  • Make dashboard snapshots clickable
  • Added #6349 - add view permission for print all assigned
  • Added Department update API endpoint
  • Added #6463 - ability to override session path in .env
  • Added #6464 - added company name to searchable field in user search
  • Added ability to upload favicon and email logo
  • Added #6099 - XML as new uploadable file type
  • Added #6241 - user license api endpoint
  • Added #6617: Added endpoint for licenses checked out to an asset
  • Added #6625 - include fully depreciated date in custom asset report
  • Added simplified slack channel regexp and allow private (no # prefix) channel

Fixed

  • Fixed #6004 - set a default next_audit_date if none provided
  • Fixed #6011 - use correct file created at date
  • Limit width of title logo so it doesn’t break with long names
  • Fixed #6013 - add accessory checkout notes to detail page
  • Fixed #5964 - Group IDs can be now be passed to user creation API
  • Fixed bug where checkout right-side menu would display assets checked out to non-users with the same ID
  • Fixed DBAL issue affecting MariaDB 10.2.7 or greater
  • Fixed #6029 - Model number not appearing in checkin/checkout emails
  • Fixes #6016 - Check for an existing username before getting creative
  • Fixed - Only allow activated users to reset their password
  • Fixed - Set activated checkbox to 1 by default on new user
  • Fixed #6082 - don’t show expected checkin in email if none given
  • Fixed MAC address regex
  • Fixed: #6263 V5 - Missing oauth tables when using the setup
  • Fixed issue where admin users could disable activation when editing their own profile
  • Fixed #6323 - typo in link for low inventory
  • Allow min:0 for consumables
  • Fixed check whether the user can edit an asset before allowing them to change the name on checkout
  • Fixed #6175 - crashing when accessory has been deleted
  • Fixed #5879 - added user department filter for custom report
  • Fixed #6386 - licenses not searching on category name
  • Fixes #6341. Adding condition that checks offset of licenses seats when the user looks other page than the first.
  • Fixed: #5896 Custom fields of type "CUSTOM REGEX" are always saved as "ANY
  • Fixed #5554 - Language of acceptance email ii admin language, not recipient language
  • Fixed bad groups route on error
  • Fixed #6350 - import page was blank on MS Edge browser
  • Fixed issue importing encrypted custom fields
  • Fixed #6644 - asset name not linked in Reports > Asset Maintenance Report
  • Fixed issue where users cannot log in with generated password
  • Fixed #6634: Asset Import History fixes and optimizations
  • Fixed #6704 - byserial asset API endpoint permissions

Removed

  • Removed gh-changelog.php - we don’t use it anymore

Improved

  • Insert audited items to the top of the list in bulk audit
  • Use username instead of email address in password reset to prevent confusion

Documentation

Want to Help Test?

Awesome! First things first, you should NOT test this in production yet, as it's a beta release. If you'd like to help us test, make a new copy of Snipe-IT and upgrade your copy to v5.0.0-beta-1.0, that way your data is safe. You should treat this test instance as a version you could easily throw away when you're done testing. (Hopefully it won't come to that, but hey, computers are hard.)

Things we're very interested in folks testing:

  • LDAP/AD integration (login and sync)
  • Using S3 to store files. We've built a little tool to help you migrate your local files to S3, which you can read about here.
  • Client-side validation

If you need to create new bug reports for this beta release, please make sure you include the beta release version in the Github issue title so we can easily see that it's an issue specific to this beta.

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.

Upgrading from v3

Please see the upgrade instructions here. After completing the upgrade below, be sure to clear your browser cookies.

Thanks!

Special thanks to @jwhulette, @patrict, @VELIKII-DIVAN, @liquidhorse, @Seldaek, @inietov, @benrubson, @NMathar, @smb, @Sxderp, @fanta8897, @andreybolonin, @shinayoshi, @reuser, @KeenRivals, @omyno, @jackka, @herroworrd, @colin-campbell, @HinchK, and @uberbrady for helping bring v5 to life!

awkward-thank-you

Assets 2

@snipe snipe released this Feb 13, 2019 · 25 commits to master since this release

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.

Assets 2

@snipe snipe released this Feb 13, 2019 · 31 commits to master since this release

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.

Assets 2

@snipe snipe released this Jan 26, 2019 · 41 commits to master since this release

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.

Assets 2

@snipe snipe released this Jan 3, 2019 · 56 commits to master since this release

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.

Assets 2

@snipe snipe released this Oct 26, 2018 · 72 commits to master since this release

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.

Assets 2
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.