Raz @ Cloudinary

Thanks for the update @mcapy.

Your account is fully enabled without any restrictions. It is up and functioning and assuming that you enter the right credentials there shouldn’t be any problem connecting to it.

I’ve also checked our logs and couldn’t find any request associated with your account that was received on our servers in the past 30 days. Therefore, I believe it indeed fails local validations and the connection request isn’t even fired.

I can try and debug it on your environment, trying to set up the connection myself, but for that, I will need temporary access to your environment, or we can try and debug it further together by you sharing some screen captures of the page when you are trying to establish the connection.
Both ways require us to continue the communication over a private channel, as sensitive information will most likely be exposed. Thus, please open a direct ticket with us via either one of the channels I provided in my last reply and we will proceed with the debugging process over the private ticket.

Thanks,
Raz

Hey @mcapy,

Are you sure that the ‘CLOUDINARY_URL=’ prefix that exits when copying the environmental variable from Cloudianry’s dashboard was removed before you were trying to save the credentials?
In case that it was removed as it should, can you please share with me your cloud name so that I can check your account’s status and our logs for additional information?

If you prefer to continue the conversation over a private channel, please feel free to open a direct support ticket at https://support.cloudinary.com/hc/en-us/requests/new or via [email protected], and I will take it from there.

Best,
Raz

Hey @riggsba,

Can you please open a support ticket at [email protected] so we can proceed with helping you in the debugging process where you can share some additional details about your environment over a private channel?

Thanks,
Raz

Thanks for the additional information @riggsba.
Upon checking our logs, I can see requests to our API coming from your site https://brunoriggs.com.br, which use you API Key and Secret, but with incorrect cloud name – dvmvbjfsx. Are you familiar with this cloud name? Any idea why the requests are made with this cloud although API Key and Secret are associated with the brunoriggs cloud?
Can you please navigate your plugin’s Connect page and check what are credentials within the environmental variable? If you see the incorrect cloud name is used there, then change it to the correct one, then try again.

Let me know if that solved the issue for you?

Best,
Raz

Hey @riggsba,

This is most likely an issue with the Cloud Name<=>API Key combination provided in the plugin’s credentials.
Can you please share you Cloud Name with me, so I can find the request in our logs and provide you with more details?

Thanks,
Raz

Hi @ash_hitch,

We’ve just released the new version of the plugin (v2.2.0) a few days ago.

Can you please confirm whether this version fixed the problem for you?

Thanks,
Raz

Thanks for the additional information @ash_hitch.

The upcoming release should fix the issue that you currently experience.
We expect the release to take place either this week or the next one.

Please monitor your plugin updates closely so once the new version is out, you will be able to install it right away.

Thank you for your patience and understanding and sorry for the inconvenience.

Best,
Raz

Hi @ash_hitch,

Thank you for reporting this.

In order to be able to further investigate the issue you’re experiencing, may I kindly ask you to provide me with the following details:

* WordPress version
* The theme that you use and its version
* A full list of all other plugins that you have installed on your environment
* Page builders that you actively use

In addition, may you kindly let us know if you’ve seen this error triggered on your environment with previous version of our plugin or it only started happening with 2.1.19? What was the previous version you had installed before upgrading to the current version?

Thanks,
Raz

My pleasure @chevindu!

Please let me know if you still run into any issues after making sure the file names are different.

Hey @chevindu,

Cloudinary uses a combination of resource type (i.e. image, video, raw), type (i.e. upload, private, authenticated) and public id (which is the file name excluding the extension) as the external unique identifier of an asset. This means that two assets with the exact same combination of values cannot co-exist on your Cloudinary account, and one will overwrite the other. Therefore, if you do have two images like that, this is most likely the cause for the wrong image/s that you see in one or some of your posts.
Let me know if this is indeed the case?

Best,
Raz

Hi @chevindu,

Sorry for the delay in response.

Can you please check if the images that are replaced and those which replace them share the same file name?
It can be also images with the same file name in your WP uploads folder but with a different file extension.

Thanks,
Raz

Hi @chevindu,

Can you please share with me what plugins you use, your WordPress plugin version, the operating system the server is running on and the version Cloudinary’s plugin that is installed on your environment?

Thanks,
Raz

Hi @diogocardoso2010,

Upon taking a look at your site and picking up some random product images, I do see they are delivered with the f_auto and q_auto transformation parameters, along with some others and the image format I get back on a Chrome browser is WebP.

Can you please share with me some image URLs where you see this isn’t happening? Or at least direct me in the right place of how to reproduce this issue on your site? Any specific page I should navigate to?

Thanks,
Raz

Hi Praveen,

Would you care to elaborate more on your last comment, I’m not quite sure that I understand the current issue.
What do you mean by “I tried reinstalling the Cloudinary with new API”?
You stated that the URLs of the images were changed back for delivery via your local WP server, which is the intended result.
Nevertheless, it seems like you still experience an issue in that area. Are your image URLs broken after the plugin was uninstalled and the delivery URLs were changed to the local server? If so, can you please share an example image URL after the uninstallation had taken place, showing the broken URL with its full path?

Thanks,
Raz

Hi @danielahross,

Is the URL that you’ve shared:
https://res.cloudinary.com/de1c27uwb/image/upload/$wpsize_!woocommerce_single!,w_960,h_650,c_scale/v1590147068/Screenshot-2020-05-21-at-14.38.31.png,
where the global transformations are omitted completely is retrieved from the src of the image tag or from any of the breakpoints within the srcset attribute?

Thanks,
Raz