Skip Navigation

[Resolved] public_queryable Not Saving Change

This thread is resolved. Here is a description of the problem and solution.

Problem:

The issue here is that the user is unable save their custom post type settings.

Solution:

What I would recommend that you do is to temporarily disable the non-toolset plugins and try again as it seems that a plugin is causing this issue to occur.

This support ticket is created 6 years, 1 month 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 keithT-3 6 years, 1 month ago.

Assisted by: Shane.

Author
Posts
#1125437

I am trying to: set public_queryable to unchecked and set exclude_from_search to be checked but the change is not saving.
This is what I want - hidden link

Link to a page where the issue can be seen: on back end

I expected to see: when I click to save post type I only get a spinning ball and the change is not saved. This - hidden link

Instead, I got:

#1125549

Shane
Supporter

Languages: English (English )

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

Hi Keith,

Thank you for contacting our support forum.

From your debug data I see that you have quite a number of plugins installed. What I would recommend that you do is to temporarily disable the non-toolset plugins and try again as it seems that a plugin is causing this issue to occur.

Thanks,
Shane

#1127515

My issue is resolved now. Thank you!