A small conflict with another ACF plugin on front-end

Hello,

Thanks for the feedback. I just tested the Image/File field and it works as expected. However, you should know that ACF Extended add a new setting in those fields allowing to override the “Uploader Type” for each field.

Can you check that you correctly set “Browser” in the “Uploader Type” setting of your Image Field?

I just noticed that this field setting override the acf_form() general uploader setting tho. I’ll add a “Default” setting option in the Image/File fields settings in the next patch to fallback to the default ACF & ACF Form behavior, to avoid overriding it when needed.

Have a nice day!

Regards.

Hi Konrad,

Thank you for your reply.

I now see that i have not described the issue properly, sorry for the confusion.

This plugin adds it’s own field type called “Image Aspect Ratio Crop”, the field uses default setting for the uploader on front-end. The issue occurs when this field used with ACF Extended in a repeater on front-end and when the repeater row is added, but after the page with the form is reloaded, the upload field becomes basic.

I’ve made two screenshots to show how it looks:

View post on imgur.com

The first image show the upload field after the row just added, the second image show the same field after the form is saved.

Hello,

Thanks for the feedback! I don’t use ACF Crop Image, so I didn’t know it has its own field. I just tested with the plugin field, it still works correctly with and without ACF Extended. See video: https://i.imgur.com/2PVzETy.mp4

If you’re using acf_form() please make sure to correctly add acf_form_head() before the get_header() in order to enqueue the ACF JS on front-end. You could also check your browser console, maybe you got a JS error? I also tested with ACFE Form, it also works correctly.

I would recommend to try with a simple Field Group, with only one repeater and one ACF Crop image field (maybe you got a compatibility issue with an another plugin/field?).

Regards.

Hi Konrad,

I’ve made more test, checking how the acf_form() is added, made the options turning on and off in Flexible Content and found that it happens only when the “Layouts: Asynchronous” option is turned on. Besides that it works perfect without any issues.

Thank you very much for taking time looking into it and your replies.

Regards.

Hello,

Ah! Nice find! Yeah now that makes sense, since when you use the “Async Layouts” feature, the fields that are added when you click on “Add Row” are retrieved from an Ajax Request. In this ajax request, your custom setting 'uploader' => 'basic' isn’t loaded (since it’s only used in the acf_form() page).

So yeah, one solution would be to use acf_update_setting('uploader', 'basic') as a global setting (and not only in the acf_form()), or implement it in the ajax request.

But in the end, this “Async Layout” feature was designed for very complex Flexible Content, which need some performances tweaks. If that’s not your case, you can just disable it and it will works as expected.

Have a nice day!

Regards.