Iain Poulson

Hi @rushmediastudios I’m sorry to hear you have had a bad experience with our support. We have a dedicated team that provides support to all users of ACF, with the team of engineers on hand to provide technical support. I’d be happy to try and track down your issue to investigate what happened here.

Please could you send a message via our contact form quoting this review and ask to be escalated to me – I’m Iain Poulson, the product manager for ACF.

Hi @jonte98, ?Iain here, the product manager for ACF over at WP Engine.

Thanks for raising these concerns. We have a performance task on our backlog and will add this to it, but we’ll look into the increased memory issue.

When ACF was enabled it increased by 2MB in RAM. Which is a lot more RAM usage than Meta Box.

Is this on the frontend of the site or in the wp-admin?

Will keep you posted.

• This reply was modified 1 year, 7 months ago by Iain Poulson.

Thanks for letting us know, @milesgilmour – great to hear ??

@nanny7 If you were to purchase ACF PRO and install it on sites which have the legacy add-ons, you should be able to simply deactivate (and delete) the add-ons and your ACF fields will continue to work as is. We would always recommend taking a site backup before making upgrades like this.

Just an update on this.

The plugins were supported for the duration of ACF 5, and continue to work on ACF 5.12.5, our latest release of ACF 5.

Those plugins will not behave as expected in ACF 6 or future versions, with various CSS errors appearing in the new UI. We do not recommend their use with any version of ACF beyond 5.12.5.

ACF 6.1 contains significant changes to the internals of ACF. Many file paths have changed, so legacy plugins which support subfields will no longer show the “subfields” section when editing the field.

If you wish to manually maintain these legacy add-on plugins, you will need to regain the subfields section in the field editor. You can do so by editing the $plugin/includes/5-7/$plugin_name.php file, and replacing:

acf_get_view('field-group-fields', $args);

With:

acf_get_view( 'acf-field-group/fields', $args );

Hi @milesgilmour this should be fixed in 6.1.2 released earlier today. Please let us know how you get on.

Hi @sonjoe

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.

That being said, we will look into why they worked for you in 6.0.7 and not in 6.1 and if it’s possible to get them working again without a large amount of development, we will.

Please can you send on a the issue you are having (error messages, screenshot, debug log) to our support team through the form on https://www.advancedcustomfields.com/contact/.

?Hi @davefx, Iain here, the product manager for ACF over at WP Engine ??

Thanks for the heads up, we’ll get this logged on our internal tracker and investigated. I’ll resolve this ticket for now, but will update you when we move forward with it.

Thanks for the report @chargeup – we have seen this too and will be getting it fixed in the next version and in our documentation.

Ahh, gotcha. Thanks for the clarification – will get that fixed up.

Hi @peterlohde, thanks for the feedback. We agree! We are making a change to the menu in ACF 6.1 to make it ‘ACF’ instead of ‘Custom Fields’, which should solve the translation issue.

Thanks for the heads up @tobifjellner. Which language is this for? We have all the strings managed in w.org, would you mind submitting an update to it here https://translate.www.ads-software.com/projects/wp-plugins/advanced-custom-fields/? Thanks ??

Hey?@ukrainaevents?the support team and developers don’t always monitor the support forum, due to how we provide support via email, please check our note here?https://www.ads-software.com/support/topic/free-support-expectations-and-response-times-7/.

Feel free to ask our support team via https://www.advancedcustomfields.com/contact/

Hey @ukrainaevents the support team and developers don’t always monitor this support forum, due to how we provide support via email, please check our note here https://www.ads-software.com/support/topic/free-support-expectations-and-response-times-7/.

Feel free to ask our support team via https://www.advancedcustomfields.com/contact/

Hey @igenlabs, I’m the product manager for the plugin and appreciate the feedback. We understand that a change to a long-standing UI can be jarring and breaks some muscle memory. We have a lot of happy users of the new UI and we are also listening to constructive feedback about how it can be improved. You can see we have been refining, improving and fixing issues with the UI since 6.0 with a big release in 6.0.6 allowing users to remove the tabbed field settings view – https://www.advancedcustomfields.com/blog/acf-6-0-6-release-flexible-content-field-layout-improvement/#disable-tabs-field-settings