Issue with uploaded S3 images after moving from 2.11 to 3.1 #4499
-
Hi all, I have recently upgrade from 2.11 to 3.1, and unfortunately found out after pushing to prod that none of the previously uploaded images work. I have had to temporarily hide them on the live to allow it to still be usable, but it is a bigger issue internally as we cannot manage any orders due to /edit erroring when also trying to find the images. The main error that occurs is: Beforehand on 2.11 my setup was done the following:
This unfortunately won't deploy to Heroku due to an error I found @kennyadsl recommend a solution to this problem which I've added + deleted my I have also tried:
I am really not sure where to go from here, but it is a pressing issue that I really need some help with. It's probably something small but I am not greatly familiar with this side of the codebase so I am currently in the dark as to what I'm actually doing. Essentially, what I need is our old 2.11 images to be accessible and usable on this new 3.1 version. MANY thanks in advance! 🙌🏻 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Did you add config.image_attachment_module = 'Spree::Image::PaperclipAttachment'
config.taxon_attachment_module = 'Spree::Taxon::PaperclipAttachment' to the |
Beta Was this translation helpful? Give feedback.
Did you add
to the
spree.rb
? By default, Solidus it's trying to use ActiveStorage now and you have to instruct it to behave as before.