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.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When entering the initiatives view on the development environment of Decidim (initiated prior to Active Storage feature and migrated with the Active Storage migrations), it will throw this kind of an error.
The system had previous initiatives attachments from CarrierWave and the Decidim upgrade migrations were run after #7598 was merged.
I am not sure if this is still ongoing work as there is still one PR open regarding the Active Storage migration #7902.
Extra data (please complete the following information):
Device: (any)
Device OS: (any)
Browser: (any)
Decidim Version: current develop branch
Decidim installation: development installation
Additional context
It seems that this case happens when:
The initiative has an attachment
The attachment has a file record (Active Storage)
The attachment url is set to nil (I don't know why)
It also seems the blob object is not available for these old attachment files, which probably means they haven't been converted to Active Storage blobs yet (and I did not find any migration tool to do that or any documentation/changelog notes about that)
Describe the bug
When entering the initiatives view on the development environment of Decidim (initiated prior to Active Storage feature and migrated with the Active Storage migrations), it will throw this kind of an error.
The system had previous initiatives attachments from CarrierWave and the Decidim upgrade migrations were run after #7598 was merged.
I am not sure if this is still ongoing work as there is still one PR open regarding the Active Storage migration #7902.
To Reproduce
Steps to reproduce the behavior:
decidim:upgradeanddb:migrateExpected behavior
I would expect the initiatives view to work as it used to.
Screenshots
If applicable, add screenshots to help explain your problem.
Stacktrace
Extra data (please complete the following information):
developbranchAdditional context
It seems that this case happens when:
urlis set tonil(I don't know why)blobobject is not available for these old attachment files, which probably means they haven't been converted to Active Storage blobs yet (and I did not find any migration tool to do that or any documentation/changelog notes about that)