Liam Gladdy

Cheers @willwenzel, not least for reminding me this plugin still exists!

I’ve bumped tested up to so you won’t get the warning. I’ll do a proper release this weekend with version bumps and make sure everything ticks along for another few years ??

Hey @davidginzberg,

Really sorry about this. Looks like we had an issue with the deployment that’s now resolved. If you redownload the plugin from www.ads-software.com it should work correctly now, but please let us know if you have any other issues.

Thanks,
Liam

This issue was caused by acf_add_local_field_group being called too early, before ACF had been initialised. Whilst it’s fixed in ACF 6.1.2, we would still advise you update your code.

You should wrap any calls to acf_add_local_field_group inside an action hooked to acf/include_fields, such as:

add_action( 'acf/include_fields', function() {
    //acf_add_local_field_group code
} );

• This reply was modified 1 year, 7 months ago by Liam Gladdy.

@nanny7 Hey there, as Iain said above:

Unfortunately the ACF addons (Repeater, Gallery, Flexible Content and Options Page) were discontinued when ACF 5 was released back in 2018 by Elliot, and are no longer available for purchase or receiving updates. They are deprecated plugins that are only compatible with ACF up to version 5.12.

We’re currently still back porting security releases in ACF 5.12, with 5.12.5 released just this week, so if you need these legacy add-ons without a current ACF PRO licence, you can stick on ACF 5.12.x.

Thanks!

Following further follow up on via our support system, we’ve determined this issue was caused by a file system permissions error which prevented WordPress being able to download and unzip ACF 6.1 correctly.

Because ACF 6.1 contains significant changes to our files and folder structure, permission errors might be more noticeable when upgrading to this version as WordPress cannot create new folders as part of the extraction process.

If you have similar issues, please contact your web hosting provider.

Following further follow up on via our support system, we’ve determined this issue was caused by a file system permissions error which prevented WordPress being able to download and unzip ACF 6.1 correctly.

If you have similar issues, please contact your web hosting provider.

@mullibahr Hey! Could you check if custom fields are enabled in the screen options tab at the top of the page? It could just be they’ve been hidden by a user and aren’t visible. If the checkbox is there, could you drop us an email to our support address and we’ll look into this deeper. Thanks!

@webconnect This happens when due to a plugin loading a non-full version of select2 and overwriting ours – we’ve got a patch lined up to fix this in the next day or two.

@snook4tech Your error is likely a filter or hook being applied on post save. If you send us an email to support, we can take a quick look as see if we can help here.

@ivanremi We’ve got your support ticket and someone will get back to you shortly. You can find more information on the warning in your logs here: https://www.advancedcustomfields.com/resources/acf-field-functions/ – it’s not a fatal error, and shouldn’t be the cause of any memory issue; but it’s a heads up some code is executing incorrectly and should be fixed.

• This reply was modified 2 years, 11 months ago by Liam Gladdy.

Hey @aguett,

Today’s ACF 5.11.2 release makes some changes to way the security fixes work which should solve your issues with get_field.

Please let me know if you continue to have issues!

Hey @aguett.

Version 5.11 implemented a change which prevents get_field getting fields which don’t exist or data that isn’t from ACF fields.

You can view the notes on the get_field documentation which explains what has changed and potential fixes depending on which error is causing the problem: https://www.advancedcustomfields.com/resources/get_field/

Feel free to drop us an email to the support address if you need any help and we’ll take a look at your code to get you back up and running.

Hey Tim,

Yup! This is correct. We made some changes to the build system since the last release.

Cheers,
Liam

Hey fashionandmash,

I’m really sorry about this, and the delay in replying. I only just figured out how to turn on email notifications for posts here.

I’m not too sure what happened here, because WordPress is supposed to not allow fatal errors like this to take down your site, and I do some checks to see if that OAuth class is already defined by another plugin, but clearly something went very wrong in this case.

I’ll boost the defence against this kind of thing in the next release.

Thanks!

Hey kc,

Sorry for the delay. What do you get if you:

var_dump( get_post_meta( $post->ID, 'dominant_color_hex', true ) );

Feel free to email me – [email protected] and we’ll get this sorted if you still need help!

2.0.1 is released! Sorry about this. Not sure how I didn’t notice it before!

Hey tyrann0us,

Fixed that bug. Will look into the uninstall hook for the next release too!

Thanks!
Liam

Ah, this must be some weird plugin conflict.

I’ll release 2.0.1 now with this fix in! Thanks for the heads up, so sorry for not noticing this thread for so long!