Was there any work carried out on the picture uploader today? All my picture uploader elements stopped working. The image does not get loaded into the element, however if I hover over the element it will display the file name of the uploaded picture. This is both in the live and development versions. So I don’t think it’s related to me doing anything as I haven’t touched the uploaders, and it exhibited in live before I pushed a new version.
I might be hallucinating, but did the picture uploader icon in the elements section get a new icon?
If I add a new picture uploader, it seems to work, albeit with a slight delay. Hoping to not having to replace all my picture uploaders and attached workflows.
Sometimes it’s sort of vague, so I guess it is possible. Hard to tell. You can test it by re-creating the issue on a brand new test app. If it is still an issue, then you can make a bug report and show them that test app so they can re-create the problem.
Thanks J805, yeah I did have a look there and saw that work was carried out, but as you say, hard to tell if it might have affected uploading pictures.
Yeah, as I mentioned. I tried re-creating it with a new uploader, which works. But that does not solve the issue of all the older uploaders no longer loading in the uploaded image. It’s a bit of a weird one.
Yeah, that is odd. Try just moving them one pixel and then pushing an update and see if that fixes it. So if you delete the uploaders and put in another one, it will work? That will be an irritating fix… hmm
Moving it 1px? haha that’s an interesting idea, but no that unfortunately didn’t work. Yes, I’m using a number of uploaders with workflows and conditionals attached to them, so stripping them all out and replacing them would be at the very bottom of the list for solutions.
Tried clearing browser cache, and tried on a few different browsers. Will support a bug ticket instead.
@J805 Ticket has been submitted. Your suggestion did unfortunately not solve the issue. I also tried “replacing element” with picture uploader to see if it would jolt it back into action, but no dice.
Okay, we think there’s a very high likelihood the problem is due to a deploy from 1:08 pm today. We’re reverting that deploy now, and expect it to be live in about ~7 minutes. We haven’t been able to reproduce the bug on our end yet, so I’d appreciate: a) confirmation that the reverting the code fixed it once it goes live (I’ll post again when it does), and b) any details you can send us (to support@bubble.io if it involves an app you don’t want to post on the forum) to help us reproduce so that we can identify the problem and re-deploy the offending code with the issue fixed
@josh That would line up nicely with me first seeing it around 2pm when I tried to upload an image in the live app.
I did submit a bug report with repro steps for an app, but it might not have made its way in front of the team yet. I will keep an eye out for when the deploy and give it a go.
I can confirm that it’s working in my live app now, without me deploying a new version. So looks like you might have found the offending code there! Great stuff!
