Victor @ Cloudinary

Hi @generosus,

Thanks for the feedback, we’ll pass it along!

Hi there, as you’ve noticed, the URLs are a bit odd but for multiple reasons. You’ve already pointed out the non-working URLs and the properly-working URLs, in which the former simply end in the version number (v1689156211), which won’t work. In addition, typically Cloudinary URLs contain image/upload/ in them, as opposed to images/, which does change the URL structure and the actual public ID of the image in question is blog/mukken-shop-de.

Could you please submit a support ticket at https://support.cloudinary.com/ and generate a system report to help us better investigate this for you?

https://support.cloudinary.com/hc/en-us/articles/360022260599-How-to-generate-a-system-report-on-the-WordPress-plugin-

If you could also reference ticket 250728, that would help us with tracking this conversation as well. Thanks!

Regards,
Victor

Hi @drbroad,

Just wanted to follow up and ask if you’ve had a chance to review Loic’s latest message? Please let us know if there are updates and we’d be happy to help.

Regards,
Victor

Hi there,

Thanks for the update. We’re passing this information along to the plugin dev team and will let you know once we have updates to share.

Regards,
Victor

Hi there,

Thanks for reaching out. Could you please provide the following and any other details you feel would help us replicate and diagnose the issue?

* WordPress version
* Cloudinary Plugin’s 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
* A screenshot of your Site Health under the Tools Section
* A screenshot of the issue and/or a live URL
* Hosting providers & Plan (AWS, WP-Engine, etc..)
* Multisite environment (subdomain/subdirectory)

Note that since version 2.7.0, you can use the new system report (https://cloudinary.com/documentation/wordpress_integration#system_report) feature in order to generate all the information above except the screenshots.

Thanks!

Regards,
Victor

Hi there,

The “?_i=AA” term in itself hasn’t resulted in any issues, as far as I am aware. This parameter is used to differentiate on our side if an asset is delivered through the WordPress plugin or not. If not, there is no “?_i=AA”.

I was able to access that URL via my Android browser, though that isn’t quite the same as using your app. Do you have additional details or an error message or screenshot? Please provide as many details as possible to help us diagnose the issue, thanks!

Regards,
Victor

Hi @kylephillips and @pzanno,

Thank you for your patience. The issue seems to be fixed and QA’d internally, it should be included in the v2.7.0 release. We will update you once the release is imminent or has gone live.

Regards,
Victor

Hi @oolongm ,

That could help us better assist you. If you’d like, you can open a ticket at https://support.cloudinary.com/ and include those login details for us to privately see and use.

Regards,
Victor

Hi there,

Thank you for contacting us.

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
* Cloudinary Plugin’s 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

Once provided, we will take a deeper look into it on our end, trying to reproduce the issue to better understand the root cause for it.

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?

Looking forward to your update.

Thanks,
Victor