using toolset with ACF Pro

This support ticket is created 4 years, 11 months 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
-	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	-
-	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	-

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

Tagged: Toolset Blocks

This topic contains 1 reply, has 2 voices.

Last updated by Luo Yang 4 years, 11 months ago.

Assisted by: Luo Yang.

Author

Posts

August 25, 2020 at 5:13 pm #1756949

Hung Pham

I am following this tut https://toolset.com/course-lesson/creating-a-custom-search/ All the CPT and custom fields have been created with ACF Pro. However, two problems:
1. All CPTs are reported as non-types fields.
2. Adding search field, it is showing the values such as a:1:{i:0;s:3:"691";}

Is there any way to have Toolset working with ACF Pro?

Thanks.

August 26, 2020 at 7:25 am #1757527

Luo Yang

Hello,

Q1) All CPTs are reported as non-types fields.
Please elaborate the questions with more details, take a screenshot for it.

1) The CPTs should be custom post types, they should not be custom fields
2) If we are talking about custom fields created with ACF Pro plugin, then you will see those custom fields as non-types fields, since they are not created with Toolset Types plugin
https://toolset.com/download/toolset-types/

Q3) Adding search field, it is showing the values such as a:1:{i:0;s:3:"691";}
As you can see, the field value you mentioned above is a serialized array, Toolset plugins won't support it.
Toolset plugins can not support such kind of fields of ACF Pro plugin, in your case, you can try those simple field types, for example: single line, single select fields.