Junaid Bhura

I really appreciate your feedback! ??

I think most people won’t have a problem with the width and height being in the URL, since it doesn’t really affect anything. That way the plugin can be as light as possible, with very little configuration.

For folks who want to customize the arguments, the filters are available. I’ll keep an eye out for more requests similar to yours, and if it’s something that a lot of people want, I can update the plugin!

Thanks again for bringing this up! You can feel free to raise further issues directly on Github, since it will be easier to discuss code there: https://github.com/junaidbhura/auto-cloudinary/issues

@petersplugins If I understand this correctly, you just want the full sized images which are added to the WordPress editor in the WP Admin, to not have width and height in the Cloudinary URL?

If that’s the case, I’m not sure this would be a good idea to add to plugin at this point. The good news is this plugin lets you extend it very easily. You can use the filter cloudinary_args: https://github.com/junaidbhura/auto-cloudinary/wiki/Filters#cloudinary_args

add_filter( 'cloudinary_args', function( $args ) {
	if ( $something ) { // Your condition to remove width and height.
		unset( $args['transform']['width'] );
		unset( $args['transform']['height'] );
	}
	return $args;
} );

Hey @petersplugins

Glad you find this plugin useful! ??

I’m not sure I fully understand what you mean. Could you please share an example?

Yes, that’s right. It won’t count the transformation again if it has already done it once before. You can contact Cloudinary support to clarify.

I wouldn’t recommend modifying the plugin’s code, because you will lose these changes when the plugin updates the next time. You can try to use WordPress hooks instead. Here’s a list supported by this plugin:

https://github.com/junaidbhura/auto-cloudinary/wiki/Filters

I’m afraid you’re going to have to figure this out on your own, depending on your code ??

Hi there @cakriwut

Thanks for your rating, and blog post!

Cloudinary gives you two options to auto fetch. The first is the option mentioned in your post:

https://res.cloudinary.com/demo/image/fetch/https://upload.wikimedia.org/wikipedia/commons/0/0c/Scarlett_Johansson_Césars_2014.jpg

The second option is with an auto mapping folder, which this plugin uses:

https://res.cloudinary.com/demo/image/upload/remote_media/commons/2/29/Marcelo_Facini.jpg

Both these methods work. More info here (scroll down further):
https://cloudinary.com/documentation/fetch_remote_images#configuring_auto_upload_url_mapping

So the instructions on the plugin are not obsolete, it just uses a different technique than in your blog post ??

Here’s the full setup instructions for this plugin:
https://github.com/junaidbhura/auto-cloudinary/wiki/Setup

Hi there @imtino

Unfortunately, that’s how this plugin works, because it has to deal with dynamic image sizes.

As far as transformations on Cloudinary go, the transformation is only counted the first time that image is generated:

https://support.cloudinary.com/hc/en-us/articles/203619481-How-does-Cloudinary-count-transformations-

You can probably contact Cloudinary support for any clarifications regarding their pricing.

I’ve released an update which fixes the issue!

I’ll have to take a look at the code, I wouldn’t recommend hard-coding any changes at the moment. I’ll try to get the update out over the next couple of days.

Thanks for bringing this up. All development for this plugin happens on Github. I’ve created an issue there. You can keep a track of this issue here:

https://github.com/junaidbhura/auto-cloudinary/issues/1

I’ll take a look at it soon and release an update to the plugin.

Hey @yo-l1982,

Thanks for bringing this up. I’ve created an issue for this in Github: https://github.com/junaidbhura/fly-dynamic-image-resizer/issues/19

I’ll take a deeper look into this issue, and add an update on Github. You can feel free to participate on this issue, and directly create future issues on Github, because that’s where all the development happens.

Hi there,

You should leave the URLs field as is to: https://res.cloudinary.com . More info here: https://github.com/junaidbhura/auto-cloudinary/wiki/Setup

Is the box “Automatically use Cloudinary for all images” checked? If so, this plugin will try to change all URLs that match your website’s URL to the Cloudinary URL.

Hey @mvaneijgen

This is not possible with this plugin. The idea behind this plugin is for you to be able to turn this off and on whenever you want.

Hey there,

As the plugin’s description states, this plugin is only for theme developers.

So this would be used by the developers of BeTheme, and not by you!

@chladog A new update is now available with this feature ??

You can refer to this page for the documentation:
https://github.com/junaidbhura/fly-dynamic-image-resizer/wiki/Functions

Hi there,

That’s a good idea! I’ve created an issue on the Github repo: https://github.com/junaidbhura/fly-dynamic-image-resizer/issues/14

It should be part of a future version. Cheers!