I was able to upload images to Cloudinary using the normal “file upload” component, but that didn’t much of control to choose my custom Public ID, for the images.
is there any way to upload images to Cloudinary, and being able to control the Public ID
am using this block of codes, but it gives me an undefined image…
this is the screen which am trying to develop, in which am trying to point to the location on the map then record its information, plus three images to describe it, the data will be saved in firebase, and the images in cloudinary, but i was hoping the be able to upload and delete images, uploading was easy but the delete part was the very difficult part
I want to use the photo which i select it from the photo library, but it always gives me undefined file format,
I couldn’t used the image which i choose from the photo library
Thank you for the reply… is that means, i have to convert my local files (images) to Base64 stream before sending them the cloudinary,!!?
could you please give me an example
thank you muneer, it is clear and simple.
one question, please.
am thinking to use Airtable to store my data including the images, is this a wise choice
When you have the Base64 string and you store it in any kind of storage then viewing it is as simple as retrieving the string and assigning it to an image component because it accepts Base64 directly to be the image to display.
This way, you store the Base64 in the table and you do not need to convert it to image again.
In this demo it just reads the Base64 and assign it to an image and to a label but you can of course save it in any kind of database you wish to be retrieved later.
Thank you very much muneer for the example. it makes it very clear. the concept is simple…
my problem with Cloudinary is the deleting part because I have to send the image to Cloudinary then retrieving back the URL, display it, and then delete it. also there is a problem of making custom Public Id, to be honest, I don’t know how to do that part especially when am using media upload component, not web api.
There’s always more than 1 way for the cookie to crumble. The solution I shared opens doors for when our file picker/base64 converter is released! I also plan to show how to make authenticated calls to firestore and a few other things.
Also, if hashify ever stops working, we’ll need a another solution.
I plan to document both approaches eventually so we dont have to sort through forum posts
I’ll start worrying when GAS (Google Apps Script) stops working. Hashify website is easy but it only does a small JavaScript routine that you can design yourself as a Web App or use GAS to make it as a Web API.
I was able to delete images after I uploaded them to Cloudinary.
the idea was simple, what I did, I extracted the Public_id from the URL , then I used it to delete the uploaded image.
I don’t know is this a correct method, or there is a better way to do it