Skip Navigation

[Resolved] Using different format with Divi Field value

This support ticket is created 3 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.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10: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/Kolkata (GMT+05:30)

This topic contains 1 reply, has 2 voices.

Last updated by Minesh 3 years, 11 months ago.

Assisted by: Minesh.


Tell us what you are trying to do?
So I am trying to use a toolset custom field within a divi module field. I know there used to be a method of getting custom fields or values in a module with a format like this:
{!{wpv-post-excerpt item="@featured-post.parent" length="45" count="word" more="..."}!}

Where instead of using the brackets typical shortcode format. Is there a way to get this format to work with custom fields so something like this?
{!{wpcf-CUSTOMEFIELDSLUG output='raw'}!}

The reason is I am using a dynamic template within divi to have all of my posts fit a format. I know Toolset has the ability to do this, but I would rather try to use Divi as it is used for all other templates for the site.



Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

There is no alternate way to display that shortcode.

There are two ways you can display custom fields. Using Types shortcode:

{!{types field='your-field-slug' output='raw'}!}{!{/types}!}

You could try:

{!{wpv-post-field name='wpcf-CUSTOMEFIELDSLUG'}!}
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.