Skip Navigation

[Resolved] YouTube is not visible on front-end.

This support ticket is created 4 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
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: Africa/Casablanca (GMT+01:00)

This topic contains 3 replies, has 2 voices.

Last updated by chulj 4 years, 6 months ago.

Assisted by: Jamal.

Author
Posts
#1710899
유튜브2.GIF
유튜브1.GIF

I'm building a house-post-type 'Template for Housing' and YouTube isn't visible at the front end.

hidden link

#1711111

Hello and thank you for contacting the Toolset support.

This seems like a compatibility conflict with a theme or a plugin on your installation, please check if this issue appears when:
- Only Toolset plugins are activated. It will tell us if there is an interaction issue with another plugin.
- The theme is set to a WordPress default like Twenty Fourteen. It will tell us if there is an interaction issue with your theme.
If the problem disappears, start activating one at the time to track where the incompatibility is produced.

If it does not help, I would like to access your admin area and check this content template and the custom posts closely. Your next reply will be private to let you share credentials safely. ** Make a database backup before sharing credentials. **

#1713623

The content template is meant to be used in The "주택" archive. It will be used for each post in the archive loop as long as there is no Toolset Archive template assigned to that archive.

Can you explain what would you like to do and I'll help to implement it?

#1714403

I figured out the reason. Writing field names in Korean creates problems. As I changed the field name to English, it works normally.