Skip Navigation

[Resolved] The archive doesn't work properly.

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 4 replies, has 2 voices.

Last updated by chulj 4 years, 6 months ago.

Assisted by: Jamal.

Author
Posts
#1711025
아카이브1.GIF

The "주택" archive doesn't work properly and you can't see photos and YouTube from the front-end.

#1711167

Hello and thank you for contacting the Toolset support.

Can you share a URL where we can see this issue?

It seems like a compatibility bug with the theme or another plugin. 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.

#1711571

hidden link

#1713621

Thank you for your feedback.

I used credentials to your website for another ticket and it turns out that you are configuring the homepage to use a specific page, but none is selected. Check this screenshot hidden link

The "주택" archive is also not configured to be the archive for the default post type "Posts", so it won't be used in the frontend.

Maybe, I am missing something else. I'll need more details about your use cases, I am sure you will understand that we, supporters, find it hard to understand clients sites contexts without their help.

#1714407

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