On my local test install, 1.2.0 works without issues, but after updating the docker image, my production install gives me error:
Error: Error while importing set 10294-1: Set storages with ID None was not found in the database
BrickTracker | File "/app/bricktracker/set.py", line 64, in download
BrickTracker | storage = BrickSetStorageList.get(
BrickTracker | data.get('storage', ''),
BrickTracker | allow_none=True
BrickTracker | )
BrickTracker | File "/app/bricktracker/metadata_list.py", line 123, in get
BrickTracker | raise NotFoundException(
BrickTracker | ...<4 lines>...
BrickTracker | )
BrickTracker | bricktracker.exceptions.NotFoundException: Set storages with ID None was not found in the database
When i try and add a new set.
On my local test install, 1.2.0 works without issues, but after updating the docker image, my production install gives me error:
Error: Error while importing set 10294-1: Set storages with ID None was not found in the database
````
BrickTracker | File "/app/bricktracker/set.py", line 64, in download
BrickTracker | storage = BrickSetStorageList.get(
BrickTracker | data.get('storage', ''),
BrickTracker | allow_none=True
BrickTracker | )
BrickTracker | File "/app/bricktracker/metadata_list.py", line 123, in get
BrickTracker | raise NotFoundException(
BrickTracker | ...<4 lines>...
BrickTracker | )
BrickTracker | bricktracker.exceptions.NotFoundException: Set storages with ID None was not found in the database
````
When i try and add a new set.
This happens if no Purchase location or Storage location is added under Set Metadata in the admin page.
It isn't necessary to select a purchase/storage location when adding a new set, but it is necessary to add the options.
This happens if no Purchase location or Storage location is added under Set Metadata in the admin page.
It isn't necessary to select a purchase/storage location when adding a new set, but it is necessary to add the options.
Fixed.
I also added a case in the template to warn that no metadata is configured rather than displaying nothing under Metadata
Before
After
Fixed.
I also added a case in the template to warn that no metadata is configured rather than displaying nothing under Metadata
- Before

- After

Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
On my local test install, 1.2.0 works without issues, but after updating the docker image, my production install gives me error:
When i try and add a new set.
This happens if no Purchase location or Storage location is added under Set Metadata in the admin page.
It isn't necessary to select a purchase/storage location when adding a new set, but it is necessary to add the options.
Phew, I was worried that no bug were introduced after so many changes 😂. I'll take a look 😁.
Fixed.
I also added a case in the template to warn that no metadata is configured rather than displaying nothing under Metadata
@gregoo Nice quick fix 👍 Pushed a new version