joppuyo

Hey folks,

Thanks for reporting this issue. I only use ACF on the backend and I have never used acf_form so there is no special handling for this use case.

When I have time I will look into incorporating this functionality into a future version of this plugin.

I have created an issue on GitHub to track the progress.

Hey!

Unfortunately, I don’t use Beaver builder and it seems like they have really limited support for Advanced Custom Fields.

It looks like Beaver builder is only limited to built-in ACF fields which means that third-party plugins like this are not supported.

I did some quick googling and you might be able to use a plugin like this to “bridge” this 3rd party field and Beaver builder.

You will need either the free or the paid version of ACF 5 to use this plugin.

Hey, now that ACF 5.8 is officially out, I can confirm that this plugin works with ACF blocks just fine.

If there are any issues, feel free to open another topic.

Thanks!

Hey,

The image is saved in the same way as normal ACF image field. All registered image sizes (thumbnails) are generated for the cropped image.

You can consult ACF documentation on how to display the image in your template: https://www.advancedcustomfields.com/resources/image/

As for your second suggestion, this is already been requested in https://github.com/joppuyo/acf-image-aspect-ratio-crop/issues/7 and I’m considering adding this option in a future update.

Hello!

The main point of this plugin is to crop images so I don’t see why there should be an option not to crop them.

If you do not need the image in specific aspect ratio, I suggest you to use the built in ACF image field.

If you are worried that there will be duplicate images if the aspect ratios are close, you’ll be relieved that this functionality is already in place. If the image size is less than half percent of the desired size, the original image will be used directly and no cropping will take place.

I hope this answers your question!

Hey,

Glad you managed to figure it out!

Hey, glad you like it!

Currently, there is no support for gallery fields. Supporting gallery would mean creating an entirely new field type, a gallery with aspect ratio support.

If you need multiple images, I would suggest using a repeater field with aspect ratio crop fields inside it instead of a gallery for the time being.

Thanks!

• This reply was modified 6 years ago by joppuyo.
• This reply was modified 6 years ago by joppuyo.

Hey,

I’m waiting until a stable version of ACF with Gutenberg blocks is released until verifying compatibility of this field.

I had a lot of issues with Gutenberg editor support with pre-release versions of ACF but it turned out that the code worked perfectly when a stable version of ACF (5.7.7) was released.

I hope this is understandable

Hey good to know about your use case!

There’s already an issue raised on GitHub about a similar case: https://github.com/joppuyo/acf-image-aspect-ratio-crop/issues/4

I’m looking into saving cropped image coordinates in the database. This way if same coordinates are used once again, the existing cropped image would be re-used instead of creating a new cropped variant.

Do you think this would help in your use case?

Hey, can you tell me more about your use case? So I can see if there is anything that can be done in the plugin to accommodate it.

In general, I have found that dealing only with “source” images is simpler for content editors.

If all the images would be visible, there would be duplicates for every image. And the image picker does not even show the image aspect ratio because the preview is cropped to 300×300.

Thanks!

Hey, apologies this took a while but this fix is now part of version 1.0.5, just release on w.org. I added some additional checks that if the resulting image size differs less than 0.5% from the original, the resizing is skipped.

Huge thanks for this idea, it helps with the performance a lot!

Hey, thanks for your suggestion, I will look into this.

If I understand correctly, this code will skip the cropping process if the image already matches the specified aspect ratio, am I correct?

I actually created a fork that does just this. Here’s the pull request on GitHub https://github.com/andersthorborg/ACF-Image-Crop/pull/59