Describe the bug
When importing a previously-exported backup of footprints from Part-DB, the EDA info is included in the exported CSV/XML/JSON/YAML (at least when exporting a "full" version), but when importing it, this data is not used and the EDA info assignments on the imported data stay empty.
To Reproduce
Steps to reproduce the behavior:
- Go to 'Tools->Edit->Footprints'
- Find a footprint with EDA information assigned (or assign some info if it doesn't exist yet), and note down which footprint it was
- Click 'New Element', tab 'Import/Export', under "Export all elements" set the verbosity level to 'full' (format doesn't matter), then click the "Export" button
- Open the downloaded file to verify the EDA info is included (it is, in my experience)
- On a different Part-DB instance, go to 'Tools->Edit->Footprints', click 'New Element', tab 'Import/Export', and then import the file downloaded at the end of step 3.
- Once it's done importing, go to the footprint noted down in step 2 (and verified in step 4), the EDA info isn't there.
Expected behavior
The imported footprint should have kept its EDA info.
Screenshots
N/A
Server Side
- Part-DB Version: 2.10
- PHP Version: 8.4
- Database Server: Postgres 18.3
Desktop (please complete the following information):
- OS: Void Linux (rolling)
- Browser: Firefox 150.0
Smartphone (please complete the following information):
N/A
Additional context
N/A
Describe the bug
When importing a previously-exported backup of footprints from Part-DB, the EDA info is included in the exported CSV/XML/JSON/YAML (at least when exporting a "full" version), but when importing it, this data is not used and the EDA info assignments on the imported data stay empty.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The imported footprint should have kept its EDA info.
Screenshots
N/A
Server Side
Desktop (please complete the following information):
Smartphone (please complete the following information):
N/A
Additional context
N/A