I am using a custom field "team-headshot" from Advanced Custom Fields, particularly because I am using the "Advanced Custom Fields: Image Aspect Ratio Crop" plugin, which allows my end-users the ability to crop a newly-uploaded photo the exact specs required.
I also have another ACF custom field "team-role" which is a simple text field.
I was able to make these two fields available to Toolset by going to Settings > Front-End Content > Hidden custom fields.
I am successful in adding the "team-role" data to a Paragraph block in the WordPress Archive Loop, by selecting Dynamic Sources, Content, and Current Team Member. "team-role" is available in the dropdown and it displays as expected.
However, I cannot seem to do the same with the "team-headshot" image. The full listing of fields/custom fields is available when adding a Paragraph block, but when I add an Image block - either the default Gutenberg image block or the Toolset image block - I do not get the custom fields. All I see is "Author Picture URL".
Two questions:
1. How might I access the ACF field to display the image in the loop?
2. Does Toolset offer a similar function, where my end-user can crop their image to specific dimensions when they upload the file? If so then I could just use Toolset alone and not worry about ACF. The image crop is the only reason I'm not using a Toolset field group.
We are aware of the issue where the image dynamic source doesn't show the custom fields. 1. How might I access the ACF field to display the image in the loop?
What you can do is to use the single field block to display the images however you won't have the options that would normally appear on the image blocks to customize the image display.
2. Does Toolset offer a similar function, where my end-user can crop their image to specific dimensions when they upload the file? If so then I could just use Toolset alone and not worry about ACF. The image crop is the only reason I'm not using a Toolset field group.
No the image will need to be modified before it is uploaded to the website.
I ended up going about this a different way. Rather than use Gutenberg blocks in the Archive loop, I instead inserted a Content Template built with the Classic Editor. I then created the content template the old fashioned way, using an ACF shortcode. I've got the result I need on the frontend and also can continue to use the image-crop field from ACF which is better for the client in the backend.
I try to use Gutenberg as much as possible, and also try not to mix ACF and Toolset if I don't have to. Whenever possible I use Toolset custom fields when working with my custom post types. But this was an instance where it made the most sense to go ahead and do those things.
