Title: Liam Gladdy's Replies | WordPress.org --- # Liam Gladdy [ ](https://wordpress.org/support/users/lgladdy/) * [Profile](https://wordpress.org/support/users/lgladdy/) * [Topics Started](https://wordpress.org/support/users/lgladdy/topics/) * [Replies Created](https://wordpress.org/support/users/lgladdy/replies/) * [Reviews Written](https://wordpress.org/support/users/lgladdy/reviews/) * [Topics Replied To](https://wordpress.org/support/users/lgladdy/replied-to/) * [Engagements](https://wordpress.org/support/users/lgladdy/engagements/) * [Favorites](https://wordpress.org/support/users/lgladdy/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 55 total) 1 [2](https://wordpress.org/support/users/lgladdy/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/lgladdy/replies/page/3/?output_format=md) [4](https://wordpress.org/support/users/lgladdy/replies/page/4/?output_format=md) [→](https://wordpress.org/support/users/lgladdy/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields (ACF®)] Deactivated ACF conflicts with WooCommerce Product page metaboxes](https://wordpress.org/support/topic/acf-conflicts-with-woocommerce-product-page-metaboxes/) * Plugin Contributor [Liam Gladdy](https://wordpress.org/support/users/lgladdy/) * (@lgladdy) * [1 year, 5 months ago](https://wordpress.org/support/topic/acf-conflicts-with-woocommerce-product-page-metaboxes/#post-18260835) * Hey there, * Are you able to see the meta boxes in “screen options” at the top, unticked? It may just be you need to either show them, or toggle them off/on. * ACF won’t move your meta boxes, but if you’ve dragged them to display after an ACF element, WordPress might store that as their location. Once deactivated, ACF is unable to run any code to help solve this, but you should be able to solve it yourself inside screen options. * Thanks, Liam * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields (ACF®)] ACF unable to perform validation due to an invalid security nonce?](https://wordpress.org/support/topic/acf-unable-to-perform-validation-due-to-an-invalid-security-nonce/) * Plugin Contributor [Liam Gladdy](https://wordpress.org/support/users/lgladdy/) * (@lgladdy) * [1 year, 6 months ago](https://wordpress.org/support/topic/acf-unable-to-perform-validation-due-to-an-invalid-security-nonce/page/4/#post-18230328) * [@room34](https://wordpress.org/support/users/room34/) We should definitely only be running that function if we have ACF validation to perform. I’ll ask the team to check if that’s the case. * It is possible to assign ACF fields to menus, which is why we would be attempting validation, but we should bail if there aren’t any ACF Fields. * We’ve not be able to reproduce this though our side, even with big menus – that’s why we’ve asked everyone here to email. If anyone is able to give us a reproducible case, I’m confident we can fix this quickly. If you’ve already opened a ticket with support, please ask your agent to transfer the issue to me (Liam Gladdy), and I’ll pick it up directly with you. * If you’ve not opened one yet, but can provide us a reproducible test case we can login to, please mark your ticket FAO Liam, and we’ll fix it in our next release. * We need to understand what is being sent on the validation request for your site [@room34](https://wordpress.org/support/users/room34/) if you’re not using ACF fields on menus, and for that we need the full request data (or to be able to trace live in our browsers, if you’re able to give us the log) – and for security we don’t want folks sending those here on the forum. * Cheers, Liam * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields (ACF®)] There has been a critical error on this site.](https://wordpress.org/support/topic/there-has-been-a-critical-error-on-this-site-4/) * Plugin Contributor [Liam Gladdy](https://wordpress.org/support/users/lgladdy/) * (@lgladdy) * [1 year, 6 months ago](https://wordpress.org/support/topic/there-has-been-a-critical-error-on-this-site-4/#post-18205505) * [@itemm](https://wordpress.org/support/users/itemm/) ACF is fully tested with the latest WordPress release and there are no widespread issues with fatals. Every case we’ve had through to support has been a conflict with a third party plugin. Please contact our support team so they can help you find out your issue. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields (ACF®)] There has been a critical error on this site.](https://wordpress.org/support/topic/there-has-been-a-critical-error-on-this-site-4/) * Plugin Contributor [Liam Gladdy](https://wordpress.org/support/users/lgladdy/) * (@lgladdy) * [1 year, 7 months ago](https://wordpress.org/support/topic/there-has-been-a-critical-error-on-this-site-4/#post-18203919) * Hey there, * Please contact our support team at [https://www.advancedcustomfields.com/support/](https://www.advancedcustomfields.com/support/) who will help you find the error logs and see what’s happening here. * Thanks, Liam * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields (ACF®)] Wordfence alert on changed files](https://wordpress.org/support/topic/wordfence-alert-on-changed-files-2/) * Plugin Contributor [Liam Gladdy](https://wordpress.org/support/users/lgladdy/) * (@lgladdy) * [1 year, 7 months ago](https://wordpress.org/support/topic/wordfence-alert-on-changed-files-2/#post-18200530) * Hey again [@syzygist](https://wordpress.org/support/users/syzygist/), * It does look like WordFence is warning you that you’re on the Direct install of ACF which has different files than the WordPress.org version, as it’s able to contain it’s own updater. * We’ll look to fix this in our next release, or work with Wordfence to stop the warnings sooner if we’re able. * Thanks, Liam * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields (ACF®)] Wordfence alert on changed files](https://wordpress.org/support/topic/wordfence-alert-on-changed-files-2/) * Plugin Contributor [Liam Gladdy](https://wordpress.org/support/users/lgladdy/) * (@lgladdy) * [1 year, 7 months ago](https://wordpress.org/support/topic/wordfence-alert-on-changed-files-2/#post-18200359) * Hey there, * We have released a new version of ACF. Is not possible for us to modify files outside of a release, so if you’re receiving this notification you do likely have local modifications. We’d recommend reinstalling ACF to ensure you’re on a genuine copy of all the files. * Forum: [Reviews](https://wordpress.org/support/forum/reviews/) In reply to: [[Dominant Color] 10 Stars!](https://wordpress.org/support/topic/10-stars-28/) * Plugin Author [Liam Gladdy](https://wordpress.org/support/users/lgladdy/) * (@lgladdy) * [2 years, 3 months ago](https://wordpress.org/support/topic/10-stars-28/#post-17689648) * Cheers [@willwenzel](https://wordpress.org/support/users/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 🙂 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Gutenberg Blocks - ACF Blocks Suite] Fatal Error in version 2.6.10](https://wordpress.org/support/topic/fatal-error-in-version-2-6-10/) * [Liam Gladdy](https://wordpress.org/support/users/lgladdy/) * (@lgladdy) * [3 years ago](https://wordpress.org/support/topic/fatal-error-in-version-2-6-10/#post-16889838) * Hey [@davidginzberg](https://wordpress.org/support/users/davidginzberg/), * Really sorry about this. Looks like we had an issue with the deployment that’s now resolved. If you redownload the plugin from WordPress.org it should work correctly now, but please let us know if you have any other issues. * Thanks, Liam * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields (ACF®)] Problems with layout fields included programmatically](https://wordpress.org/support/topic/acf_add_local_field_group-no-longer-visible-from-plugins/) * Plugin Contributor [Liam Gladdy](https://wordpress.org/support/users/lgladdy/) * (@lgladdy) * [3 years, 3 months ago](https://wordpress.org/support/topic/acf_add_local_field_group-no-longer-visible-from-plugins/#post-16628394) * 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: * ```wp-block-code add_action( 'acf/include_fields', function() { //acf_add_local_field_group code } ); ``` - This reply was modified 3 years, 3 months ago by [Liam Gladdy](https://wordpress.org/support/users/lgladdy/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields (ACF®)] Paid Add-ons stopped working](https://wordpress.org/support/topic/paid-add-ons-stopped-working/) * Plugin Contributor [Liam Gladdy](https://wordpress.org/support/users/lgladdy/) * (@lgladdy) * [3 years, 3 months ago](https://wordpress.org/support/topic/paid-add-ons-stopped-working/#post-16628382) * [@nanny7](https://wordpress.org/support/users/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! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields (ACF®)] Why was my post held for moderation? The new version 6.1.x caused critical error](https://wordpress.org/support/topic/why-was-my-post-held-for-moderation-the-new-version-6-1-x-caused-critical-error/) * Plugin Contributor [Liam Gladdy](https://wordpress.org/support/users/lgladdy/) * (@lgladdy) * [3 years, 3 months ago](https://wordpress.org/support/topic/why-was-my-post-held-for-moderation-the-new-version-6-1-x-caused-critical-error/#post-16628373) * 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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields (ACF®)] CRITICAL ERROR WHEN UPDATING FROM 6.1.1](https://wordpress.org/support/topic/critical-error-when-updating-from-6-1-1/) * Plugin Contributor [Liam Gladdy](https://wordpress.org/support/users/lgladdy/) * (@lgladdy) * [3 years, 3 months ago](https://wordpress.org/support/topic/critical-error-when-updating-from-6-1-1/#post-16628368) * 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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields (ACF®)] Release 5.11.3 has SERIOUS BUG](https://wordpress.org/support/topic/upgrade-from-5-11-1-to-5-11-3-has-serious-bug/) * Plugin Contributor [Liam Gladdy](https://wordpress.org/support/users/lgladdy/) * (@lgladdy) * [4 years, 7 months ago](https://wordpress.org/support/topic/upgrade-from-5-11-1-to-5-11-3-has-serious-bug/#post-15125676) * [@mullibahr](https://wordpress.org/support/users/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](https://wordpress.org/support/users/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](https://wordpress.org/support/users/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](https://wordpress.org/support/users/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/](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 4 years, 7 months ago by [Liam Gladdy](https://wordpress.org/support/users/lgladdy/). * Forum: [Reviews](https://wordpress.org/support/forum/reviews/) In reply to: [[Advanced Custom Fields (ACF®)] Released a version that breaks core get_field function](https://wordpress.org/support/topic/released-a-version-that-breaks-core-get_field-function/) * Plugin Contributor [Liam Gladdy](https://wordpress.org/support/users/lgladdy/) * (@lgladdy) * [4 years, 7 months ago](https://wordpress.org/support/topic/released-a-version-that-breaks-core-get_field-function/#post-15101186) * Hey [@aguett](https://wordpress.org/support/users/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! * Forum: [Reviews](https://wordpress.org/support/forum/reviews/) In reply to: [[Advanced Custom Fields (ACF®)] Released a version that breaks core get_field function](https://wordpress.org/support/topic/released-a-version-that-breaks-core-get_field-function/) * Plugin Contributor [Liam Gladdy](https://wordpress.org/support/users/lgladdy/) * (@lgladdy) * [4 years, 8 months ago](https://wordpress.org/support/topic/released-a-version-that-breaks-core-get_field-function/#post-15072835) * Hey [@aguett](https://wordpress.org/support/users/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/](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. Viewing 15 replies - 1 through 15 (of 55 total) 1 [2](https://wordpress.org/support/users/lgladdy/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/lgladdy/replies/page/3/?output_format=md) [4](https://wordpress.org/support/users/lgladdy/replies/page/4/?output_format=md) [→](https://wordpress.org/support/users/lgladdy/replies/page/2/?output_format=md)