Closed oppianmatt closed 7 years ago
Was there any solution on this in the end? I have a similar issue on what I'm getting back from the call_api routine on images (without Unicode in the titles) for regular upload - it's working from commandline, but not from a form, which makes me wonder about what's going in/how it's being handled.
Truly sorry for the late response. In case it's still relevant -
We have just recently deployed a new capability, which allows you to change the resource type using the rename API. A new parameter was added (to_type
) for this purpose. This is currently only supported via a direct API call, Java and Node.js SDKs (we are working on supporting it via our other SDKs in the near future). Here is an example call, which demonstrates changing an image with public id 'my_public_id' to type private :
curl https://api.cloudinary.com/v1_1/cloud_name/image/rename -X POST --data 'from_public_id=my_public_id&to_public_id=my_public_id&to_type=private×tamp=1473950489&api_key=123456&signature=d0f251a9e26e89a801abd4b62e6496d7c7164417'
Closing this thread as there was no response for over two months.
We are in the process of converting our images from upload to private and they way we were told was to use the api to 'upload' each one as you can't change type. Problem is some of our images have unicode in the public_id yet the uploaded can't handle it. Here is an example:
We get the following resource in a list of resources from the api:
We call 'upload' like so:
and then we get the following stack trace: