how to publish HTML with Toolset fields?

This support ticket is created 6 years, 6 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
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)

Tagged: Setting up custom fields, Types plugin

This topic contains 1 reply, has 2 voices.

Last updated by Christian Cox 6 years, 6 months ago.

Assisted by: Christian Cox.

Author

Posts

April 14, 2018 at 10:22 pm #666086

AlexanderN4266

Hi, by default there is WYSIWYG post field that I can use to publish HTML on the front-end via the Text editor (if I switch to it manually). However, I use CSV Importer Pro to publish content automatically. If I use it to publish HTML, it inserts raw HTML on front-end because it sends data to WYSIWYG Visual editor. Is there a possibility to publish HTML via Text Editor on auto-pilot?

April 15, 2018 at 4:36 pm #668144

Christian Cox

Hi, I'm not sure how your importer works, but if it inserts raw HTML into the database, then it should display correctly in either the Visual or Text tabs. For example, I just tested this out by creating a new post with a WYSIWYG custom field called "representation." I inserted the following raw HTML for the custom field directly into the database:

<a href="http://toolset.com">Visit toolset.com</a>

Then when I edited the post in wp-admin, you can see that the Visual tab of the WYSIWYG field was formatted correctly: I see the link text underlined to represent a link. In the raw Text tab, I see the raw HTML I inserted in the database. So there's nothing inherently wrong with putting direct HTML into the database. If you are seeing HTML code appear on the front-end of the site instead of rendering as expected, that indicates your import process is somehow translating and replacing code symbols with their HTML equivalents. That would result in the HTML markup printed on the front-end of the site, rather than being rendered as actual HTML.