Skip Navigation

[Resolved] ACF conflict with Toolset

This thread is resolved. Here is a description of the problem and solution.

Problem: I am migrating from ACF to Toolset Types custom fields, and I have created a View that shows some of these custom field values. One of my fields shows the old ACF field value and it does not seem to update when I modify the Types field value.

Solution: In this case, the field slugs are slightly different and the shortcode used to display the field used the old ACF field slug. Updating to the new Types field slug solves the problem.

Relevant Documentation:
https://toolset.com/documentation/customizing-sites-using-php/functions/
https://toolset.com/documentation/programmer-reference/views/views-shortcodes/#wpv-post-field

This support ticket is created 4 years, 1 month ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 3 replies, has 2 voices.

Last updated by amandaF-4 4 years, 1 month ago.

Assisted by: Christian Cox.

Author
Posts
#2083679

So I installed toolset, set up a bunch of things, and I had already deleted ACF and custom field types from my plugins that I was using before I got toolset. Problem is now, a bunch of custom fields under property and properties is loading in the old custom field information instead of the new custom field that I gvie it. For example, minimum investment is a custom field, and when I try to use that field and make it say $1000, it is showing the old version from ACF where it displayed $55,000. I was wondering if you could help me figure out the issue? Btw, I am using elementor but not sure if that has much to do with what is going on when it feels more like a conflict with ACF.

I just want to change the custom field minimum investment and any others that are stuck and not changing. To reproduce my issue, go into one of the properties where they are over 1000, and try to change the minimum investment to 1000, then check the page hidden link

Thank you,
Amanda

#2083775

Hi, it looks like there are two different fields for the Minimum Investment value. The old field from ACF used the slug minimum_investment, but the new Types field uses the slightly different slug minimum-investment.

You can see these fields in Toolset > Custom Fields > Post Fields, then click the Post field control button at the bottom of the page. Or just go to this URL directly:
hidden link

I see your View uses the wpv-post-field shortcode to display this information from the old ACF field slug:

[wpv-post-field name="minimum_investment"]

To display the Types field value instead of the old ACF value, you can use the Types field shortcode with the correct field slug, or use the wpv-post-field shortcode with the full Types field slug including the wpcf- prefix:

[types field="minimum-investment"][/types]

...OR...

[wpv-post-field name="wpcf-minimum-investment"]

Types fields use the wpcf- prefix in the database, and the wpv-post-field shortcode is designed to display fields using the full slug. The Types field shortcode does not require this prefix, it's assumed for you.

I left the wpv-post-field shortcode in place and adjusted the slug for you, now I see the updated field values in the results. Can you confirm?

#2083815

Yes, perfect that resolved the problem. Thank you for the very fast response and for the help. I no longer need ACF because I have toolset. So far love it much more!

#2083831

My issue is resolved now. Thank you!