• chrisdunnbirch

• in reply to: have_rows() is spitting out errors if it doesn't find the field.
• November 13, 2014 at 1:57 am

Hey, thanks for letting me know.

I just noticed the version tags on the thread, that’s a neat additional. I will tag the ACF version in any future threads.

• chrisdunnbirch

• in reply to: api-helpers.php on line 846 error after updating
• November 5, 2014 at 1:27 am

I was originally getting the same error as in the first post in this thread, now I am getting a different error with the same cause:

Fatal error: Cannot use string offset as an array in SERVERURLHERE/wp-content/plugins/advanced-custom-fields-pro/api/api-template.php on line 580

However, this error is a fatal error and immediately stops the page drawing whereas before it was simply a warning.

• chrisdunnbirch

• in reply to: have_rows() is spitting out errors if it doesn't find the field.
• November 4, 2014 at 10:18 pm

Thank you for the response.

Unfortunately I can’t seem to get the error to go away. Maybe I’m mis-understanding what you mean by ‘offending post’?

I am getting the error in various places on the website I’m working on right now:

• I’m getting on 4/5 of my ‘Services’ pages (CPT ‘single-rp_service.php’) where the 5th one has the repeater field filled in and the other 4 has it empty. I have updated all 5 of the posts and the issue persists.
• I am also getting in footer.php with the same repeater field ‘flexible_rows’, it also didn’t update here when I updated the 1 service page which uses the field.

At this point I’ve updated every page on my site and the error persists.

Any thoughts much appreciated.

• chrisdunnbirch

• in reply to: WP_Query search results with 's' and 'meta_query' at the same time.
• October 3, 2014 at 11:23 pm

Ohhh array_merge() and array_unique(), of course. Here I am looking for WordPress / ACF functions to do the job when vanilla php functions were the answer.

Thank you so much, that solved the problem perfectly.

• chrisdunnbirch

• in reply to: Image Field stays blank
• September 16, 2014 at 8:47 pm

I’m also having this issue and can’t figure out how to roll back to 5.0.7, what am I missing?

EDIT: nevermind, I figured out what the issue is and will work around it for now.

ISSUE: For those that are curious, the issue arises if you select an image with original dimensions that are smaller than the ‘Preview Size’ size you’ve set.

By default when you create an Image ACF field, the ‘Preview Size’ will be the default WordPress 150×150 ‘Thumbnail’ size. The image I was trying to select was 140×140 and ACF was struggling to find the preview image to display so it just spat out the error.

I fixed it by going back to my ACF panel and selecting my custom image size for the ‘Preview Size’, and it works just fine.

Obviously this isn’t ideal, and should be fixed in 5.0.9 but for anyone looking to avoid rolling back their ACF version and keep working in the meantime I suggest just telling ACF to use a really small ‘Preview Size’.