Part-DB 1.9.0 - Update existing parts from info providers, merge parts, part associations and more

[jbtronics]

Part-DB 1.9.0

If you like Part-DB, please consider donating to help further development. See the sponsor button on the homepage.

Update existing parts

Using the blue button in the tools tab on a part info page, you can update part info from an info provider. This means you can pull datasheets, price infos and more from digikey, octopart and more for existing parts.
You still needs to review and manually choose what infos you wanna keep

Merge parts

You can now merge two parts together: If you have created two versions of the same part by accident, then you can now merge the two versions of the part into a single one. All information like datasheets, partLots, etc. are combined.

Blue dot on newly created collection items

Newly created items of a collection, which were not persisted to database yet, are marked with a blue dot on the delete item:

This is especially useful when merging parts together or update parts from info providers.

Part Associations

You can now associate part with each other. This can for example be used to denote alternative/compatible parts, or what part replaces an obsolete part.

Full changelog

Database schema changed: You need to run php bin/console doctrine:migrations:migrate after upgrade!

New features

• Added possibility to merge two parts into one
• Allow to update existing parts from info providers
• Added possibility to associate parts with each other
• Info providers can report a price related quantity for prices (PR Respect the price related quantity if reported by the InfoProvider #421 by @d-buchmann)
• Added IPN, stocked amount and storage location columns to project BOM table view (IPN in BOM list column #418)
• Allow to put barcode versions of the IPN on labels (Label generator: Create Barcode / QR-Code with the IPN (Internal Part Number) #373)
• Allow to scan IPN barcodes with the barcode scanner and added possibility to reuse existing barcodes on part lots (vendor barcodes)
• Part-DB can now automatically detect the path for the frontend dependencies, when Part-DB is not put at the webroot. No need to recompile the assets anymore (see wrong menue design after installation #426)
• The search settings in the navbar gets persisted in the browser localStorage now (Add stock column to project bom list #429)
• Show a notice about the dependency of permissions, and show a flash warning if permissions were corrected (Can't revoke permissions for usergroup #435)
• Allow to specify a timestamp when a part stock operation was actually performed (Enter date when adjusting stock & ability to adjust dates for stock adjustment #416)
• Added an option, to immediately delete a part lot if it becomes empty during a withdrawal/move operation

Bugfixes

• Fixed behavior of BOM entries when cloning projects (PR Associate project BOM entries with correct project when cloning #433 by @d-buchmann)
• Fixed database exception in certain cases (HTTP 500 errors occur when logging in, prevent parts from loading, trying to edit  #434)
• Added an env option to allow SAML behind a reverse proxy (Help Wanted: Cannot get SSO working with Keycloak behind a reverse proxy #436)

Miscellaneous

• Updated dependencies
• Fixed some deprecations
• Updated documentation (PR Update installation_docker.md #425 by @Pyromane)

New Contributors

• @d-buchmann made their first contribution in Respect the price related quantity if reported by the InfoProvider #421

Full Changelog: v1.8.2...v1.9.0

---

This discussion was created from the release Part-DB 1.9.0.

[w0hc]

Upgraded from 1.8 to 1.9.1 and run the migration command. Now I get 500 error. I can't make heads or tails of the log, there's a LOT of junk in there for each time I attempt to load the page. Mainly some permission denied messages.

[jbtronics]

have you cleared the cache afterwards?

[w0hc]

I did not. I rolled back to 1.8.2, then upgraded to 1.9.0 which seemed to work. Last I bumped to 1.9.1 and things are working.

[w0hc]

I spoke too soon. Once I tried to save any changes the 500 error came back. Clearing the cache has not helped. And I've learned that my automatic database backups aren't working, so I can't roll back to the 1.8.2 database.
error.txt

[jbtronics]

You have run one of the commands as the wrong user, and now the permissions of Part-DBs cache folder are wrong. You must run the commands as the www-data user and not as root.

You should be able to fix this, by removing the var/cache folder inside the Part-DB folder in the container completely. Afterwards just try to load Part-DB in a browser and the cache will be recreated with the right permissions.