Hello,
I have a weweb interface where a user can modifiy the logo of the company he works for. These logos are stored in supabase and a weweb workflow uses the action “Storage | Replace a file”.
The workflow works fine and the image is updated in supabase.
When I copy the image URL in a web browser it does return the updated image. But the same URL called in weweb still retruns the “old” image.
I did find a post from september 2023 where an issue with a weweb cache is mentionned, but no solution is given to solve the problem.
How can I parameter Weweb so that the cache is refreshed when an image file is updated in Supabase?
I believe if you use a new signed image link that would force the refresh. Similarly, adding a unique query string to the URL. For instance, you can use a URL like /storage/v1/object/sign/profile-pictures/cat. jpg? version=1 (that’s what Supabase docs say for their cache; not sure if WeWeb does something else on top of it). See if that works?
Other than that, you can also do something that makes it seem like a new file - e.g. add a new transformation that the old image didn’t have and it should refresh, or changing the filename after the upsert would probably trigger a refresh too. Looking forward to others thoughts because I encountered this too.