Closed eleven59 closed 1 month ago
Hey @eleven59
Thanks for pointing out the issue. We are already working on major refactoring of the Backpack Uploader to cover this and other uploader-related problems. It's a BIG PR, which may take some time. Sorry for the inconvenience.
You can subscribe to our newsletter for the Backpack Progress report and other updates.
Hi @karandatwani92,
That sounds like a great idea. I've fixed it by overwriting the uploader for now, so no rush in that regard for me. I fully trust you'll make something much better than my hacky solution here and will happily update my project whenever you're done with that.
Thanks for the quick reply, too!
Bug report
What I did
What I expected to happen
I expected that the entry would just be saved with the new image, and the old one only getting
What happened
This throws the following error:
It has to do with this function in
Backpack \ CRUD \ app \ Library \ Uploaders \ SingleBase64Image
:As you can see this does not check anywhere whether an image actually exists in the spot where it tries to delete it.
What I've already tried to fix it
Updated all backpack packages, made a completely new model with repeatable field that only has an image. Repeated the steps under "What I did". The error remains.
Is it a bug in the latest version of Backpack?
After I run
composer update backpack/crud
the bug... is it still there?Yes
Backpack, Laravel, PHP, DB version
When I run
php artisan backpack:version
the output is: