We are using the custom storage backend feature to store our scorm packages in a media storage different from where the other assets are.
Up to now we were only testing with scorm xblocks and everything seemed fine. We realized yesterday that this custom storage backend is interfering with the storage backend otherwise used by Django. All our course assets have disappeared and we are getting a 400 error on calls to those asset urls.
I looked at the code and was wondering if maybe these lines could have an impact on all xblocks :man_shrugging:
We are using the custom storage backend feature to store our scorm packages in a media storage different from where the other assets are.
Up to now we were only testing with scorm xblocks and everything seemed fine. We realized yesterday that this custom storage backend is interfering with the storage backend otherwise used by Django. All our course assets have disappeared and we are getting a 400 error on calls to those asset urls.
I looked at the code and was wondering if maybe these lines could have an impact on all xblocks :man_shrugging:
https://github.com/overhangio/openedx-scorm-xblock/blob/833e1e1ca2bf180afc9c8adddf407c10e37f8425/openedxscorm/scormxblock.py#L532
Any idea? I'm available for a debugging session if required.