Cloudinary

@hiskingdomprophecy

Thank you for the feedback. We will add more granular control for the sync. This is something that we will have in our roadmap.

If you would like to suggest a feature, I would recommend to go to our Roadmap page to submit your idea.

Regards,
Erwin Lukas

@danigonlinea

Thanks for reaching out on this.
Is it possible to share the WP version, theme that you are using, as well as the list of plugins you have install?

Regards,
Erwin Lukas

@www404, my apologies, yes, this is confirmed a bug that we are working on the fix.

@www404, can you please share what issue that you are having?
Please open a support ticket from our support portal with the details

Marking this as resolved since this invalid URL issue is resolved in v2.0.3
If you are experiencing similar issue, please report to us via our Support portal

Hi @igalst

Thank you for reaching out to us.
We are checking on this and will get back to you.

Regards,
Erwin Lukas

Hi,

In order for us to take a deeper look into it, can you please share with us the version of the Cloudinary plugin that you use, along with your WordPress version and the version of your Litespeed cache plugin?

Hi, @trevans24 The version 2.0 of our plugin allows to choose the folder in which images would be uploaded to.

Would that help?

You could download that version from here.

Note that the plugin is currently in beta. So we recommend making sure backups are in place before doing any major changes.
also please note that in order to use version 2.0, ane previous versions should be removed (rather than just disabled)

Let us know if that helps?

Hey, @esteban88 glad to hear its currently working.

3rd party plugins might indeed collide with each other so this indeed could be the issue.

Hi @disc0v3r,

Can you please share with me the version of the plug-in that you use?

In addition, please elaborate more on what you refer to by “after your service has added individual tags”? Do you mean the changes of the URLs of the images, being returned to use your WordPress site domain instead of of the Cloudinary domain?

To compress your as best as possible without losing any visible quality, you should apply the auto quality parameter to all of your delivered images (q_auto in the URL). In addition, it is recommended that you add f_auto to your URLs, which ensures the best format is delivered to each of your clients based on the browser that they use to view your site.
Lastly, scaling or cropping your images to the size of their container is highly advised as well, to reduce the size of the delivered image when bigger dimensions aren’t necessary.

Within the Media Library section, you can search for the relevant image, click on it and apply the desired layout you would like to achieve. The new transformed version URL will be generated for you to use.

Hi @hiskingdomprophecy

We just wanted to thank you for bringing this to our attention, version number 1.1.12 has addressed this issue and it is now resolved.

Hope this helps.

Hi @whichtransfers

This might require us to take a closer look at your specific environment in order to further help.

Could you open a request with [email protected] detailing your use case?

Specifically, if you could share the WP version, and the plugin version it would help us in pinpointing this.

It might also be useful to share a video of what exactly you are seeing on your end.

Thanks.

Hi @sswainson,

Thanks for your patience in this.

Checking the plugin on our end it works as expected with php 7.

Note that we performed a small refactoring so when we check the plugin with PHP 5.3 we indeed get that error on line 688

could you make sure that both the WP site and the environment were upgraded to php7 and not just one of them?

In any case, you could work around that by doing the following:

The line:

$full_path = wp_upload_dir()[‘basedir’].DIRECTORY_SEPARATOR.$md[‘file’];

should be changed to:

$wp_upload_dir = wp_upload_dir();
$full_path = $wp_upload_dir[‘basedir’] . DIRECTORY_SEPARATOR . $md[‘file’];

Let us know the result?

Thanks @jordanairwave

You beat us to answer this ??

Yes. That is exactly right. CloudinaryUploader is deprecated and in order to upload “\Cloudinary\Uploader” should be used instead.

Hi @sswainson,

In order to better understand the issue, I need some more information. Can you please share with me the following?

Whats your WP version?
What version of the WordPress plugin did you add?
What other plugin’s do you have on your WordPress?

Also since it might be related to the specific environment you are using would it be possible to open a request at [email protected] so we could take a closer look?