using non-toolset fields in views and content templates

This support ticket is created vor 7 months, 2 weeks. 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.

Dieses Thema enthält 1 reply, hat 1 Stimme.

Zuletzt aktualisiert von Christopher Amirian vor 7 months, 2 weeks.

Assistiert von: Christopher Amirian.

Author

Artikel

October 24, 2025 at 5:43 pm #2830584

ericaG

We are using the legacy Views plugin and want to be able to get custom field info for custom post types and fields NOT created by Toolset—is there a way to make [types field='xxx'][/types] work with non-Toolset fields?

October 26, 2025 at 10:28 am #2830827

Christopher Amirian

Unterstützer

Sprachen: Englisch (English )

Hi,

Welcome to Toolset support. No — the legacy [types] shortcode only works for fields created/managed by Toolset Types. For non-Toolset custom fields, use This:

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

- Works with any post meta that’s stored under your_meta_key.
- Good for simple text/number values.
- It will not work for complex/serialized values.

Thanks.

The topic ‘[Closed] using non-toolset fields in views and content templates’ is closed to new replies.