Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Image is not deleted even when response from CloudinaryDotNet is successful #361

Open
7 tasks
portal7 opened this issue Feb 27, 2024 · 1 comment
Open
7 tasks

Comments

@portal7
Copy link

portal7 commented Feb 27, 2024

Bug report for Cloudinary .NET SDK

Before proceeding, please update to latest version and test if the issue persists

Describe the bug in a sentence or two.

Issue Type (Can be multiple)

  • Build - Cannot install or import the SDK
  • Performance - Performance issues
  • [X ] Behaviour - Functions are not working as expected (such as generate URL)
  • Documentation - Inconsistency between the docs and behaviour
  • Other (Specify)

Steps to reproduce

Executing

 var deleteParams = new DelResParams()
   {
       PublicIds = new List<string> { "wsv4vxeglcbupvmonsno" },   // Example of publicId
       Type = "upload",
       ResourceType = ResourceType.Image,
       Invalidate = true,
       Tag = "REMOVED"
   };
   
  var result = _cloudinaryClient.DeleteResources(deleteParams);
   // returns OK and Errors = null 

Error screenshots or Stack Trace (if applicable)

OS and Version

  • Linux
  • Windows
  • macOS
  • [ X ] MultiPlatform

Versions and Libraries (fill in the version numbers)

  • Cloudinary .NET SDK version - 1.25.0
  • .NET Core - 8.0.0
  • .NET Framework - 0.0.0

Repository

If possible, please provide a link to a reproducible repository that showcases the problem

@Vdeub-cloudinary
Copy link

Hi @portal7,

Do you mind sharing your cloud_name? Is it wapicom? If it is the case, as documented here, the public_id contains the folder path so in your case, you should have set the public_Id to taller/wsv4vxeglcbupvmonsno.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants