Jay @ Cloudinary

@hiskingdomprophecy I can answer while Loic is offline.

Sincere apologies for the inconvenience on this.

It is advisable to use the latest version 2.4.0 of the plugin. The new version of the plugin includes new features and various bug fixes as highlighted below:

New Features:

• Added breakpoints support for featured images
• Global transformations on both Categories and Tags pages are now collapsible
• On plugin deactivation, we will ask you to share with us the reason. It’s important to us.

Fixes and improvements:

• Fixed an issue with syncing a deleted asset
• Improved the mechanism for removing the Cloudinary account
• The warning message for exceeding the annual unit plan was revised
• Improved the Alt text syncronization from Cloudinary to WordPress
• Fixed WPBakery error when inserting an image by the WordPress editor
• Fixed AMP plugin conflict issue

Though, I do not see a reason upgrading should break your site. Is there a sandbox version of the website this can be tested before upgrading on the live site?

Looking forward to your response.

Best regards,
Jay

@alexranc

Yes, that’s correct. PAYG plan allows overages and bills based on credit utilization.
https://cloudinary.com/console/payments/upgrade/pro_PAYG/monthly

This plan will allow 2,750 Monthly Credits
1 Credit = 1,000 Transformations OR
1 GB Storage OR
1 GB Bandwidth
$0.45 Overage credit price

Let me know if this helps.

Best regards,
Jay

@pire @ajonp @entertio ,

Team is working on the bug fix and will release a patch very soon.

I’ll keep you posted here.

Best regards,
Jay

Hi @entertio ,

Thank you for reaching out.

I tried using the Cover block to publish a post and then edit it again. Do not see any see errors on the latest versions – WordPress 5.5.1 and Cloudinary 2.2.0.

Would you be able to provide step by step instructions on how to reproduce the error?

Additionally, please provide:
1. WP and Cloudinary versions
2. List of other plugins
3. Themes you are using.
4. Page builders.

Once provided, I will take a deeper look into it on our end, trying to reproduce the issue and escalate this error internally as needed.

In case it will be necessary, will you be willing to provide us with temporary access to a sandbox environment of your site where we can take a look and debug if needed?

Best regards,
Jay

Hi @dyonos,

Thanks for reaching out.

I am working internally with the team on having an option to close/disable/improve the quota notifications and will update here as soon as there is some progress on this.

Can you please provide your account cloud name to take a look at?

Best regards,
Jay

Hi @selftripsru,

I have reached out internally with your query on future updates and will update here accordingly.

Best regards,
Jay

Hi @selftripsru,

Thanks for reaching out.

It would be helpful to understand your use-case first.

Would you able to provide more details on the purpose and nature of pdf files? Are these files generated by you? Also, tells us more about which other formats you are referring to?

We want to ensure no malicious files are distributed through the service.
May I please ask you to share some details regarding the expected usage and origin of the PDFs and/or Archives that you’ll be uploading and delivering – will these be uploaded directly by users of your website/app or do you have any control over this process, such as if you’re generating the files yourself prior to uploading to Cloudinary?

Best regards,
Jay

Hi @davidcoplex,

Thank you for reporting this. We are checking this with our internal dev team and will get back to you accordingly.

Best regards,
Jay