[wpv-taxonomy-description] not rendering html from WYSIWYG editor

This support ticket is created 2 years, 3 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
-	9:00 – 12:00	9:00 – 12:00	9:00 – 12:00	9:00 – 12:00	9:00 – 12:00	-
-	13:00 – 18:00	13:00 – 18:00	13:00 – 18:00	14:00 – 18:00	13:00 – 18:00	-

Supporter timezone: America/Jamaica (GMT-05:00)

This topic contains 2 replies, has 2 voices.

Last updated by BD 2 years, 3 months ago.

Assisted by: Shane.

Author

Posts

August 10, 2022 at 3:02 pm #2435245

I have a taxonomy view that displays children of a parent taxonomy.

I have successfully output the taxonomy description using the shortcode in the view loop editor: [wpv-taxonomy-description]

However, I cannot get the description to render as html, despite being entered into a WYSIWYG editor on the taxonomy editing page - it just renders as plain text.

I have tried installing the plugin 'Allow HTML in Category Descriptions' but it doesn't make any difference.

Please could you assist?

Thanks, Nick

August 10, 2022 at 6:18 pm #2435329

Shane

Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Nick,

Thank you for getting in touch.

My recommendation here is to create a second description custom field and add your description there. This way you won't need to use the [wpv-taxonomy-description] shortcode given that it will render the field without the HTML formatting.

With the second description custom field you can render it with the HTML formatting when using the types shortcode for the Meta field.

Please let me know if this helps.
Thanks,
Shane

August 11, 2022 at 10:08 am #2435787

Thank you Shane - the original issue remains, but this is a simple workaround. Thanks for your swift assistance, Nick