View Stopped Loading On Specific CPT

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

Tagged: Views plugin

This topic contains 2 replies, has 2 voices.

Last updated by mikeC-5 4 years, 2 months ago.

Assisted by: Shane.

Author

Posts

September 22, 2020 at 3:36 am #1785069

mikeC-5

Tell us what you are trying to do? I have a CPT called "press item" that is called here (and the two sub-category links displayed there): hidden link

It is not loading the view, though the individual posts display fine: hidden link

You can see a standard archive of them at the taxonomy URL: hidden link

I tried duplicating the view as well as placing the shortcode on a new page. None of these techniques produced any results.

The other views on the site work fine, you can see by clicking through the various pages (books, news, events). It's just something about this one CPT.

September 22, 2020 at 3:36 pm #1786275

Shane

Supporter

Languages: English (English )

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

Hi Mike,

Thank you for getting in touch.

I'm a little confused, which page isn't displaying the view ? And which page is displaying that exact same view?

Can you allow me to have admin access to check on this further for you to see what is happening ?

The private fields have been enabled for your next response.

Thanks,
Shane

September 22, 2020 at 8:22 pm #1786587

mikeC-5

Strangely enough, despite all my troubleshooting and testing yesterday, the issue seems to have resolved itself. My guess is that it was on the server end. Thank you for your time!