We are experiencing an issue with Toolset on our staging WordPress environment.
We have several custom post types created through Toolset. In the Post Type settings, there is a "REST API" option. When we enable this option and save the post type, the save appears to succeed. However, after refreshing the page or reopening the post type settings, the REST API option becomes unchecked again.
Because of this, the affected custom post types are not exposed through the WordPress REST API and do not appear in:
/wp-json/wp/v2/types?context=edit
For example, custom post types such as "Jira Integrations" are visible in Toolset and exist in WordPress, but they are not REST-enabled and therefore cannot be discovered through the REST API.
What's confusing is that the same configuration works correctly in our production environment, but on staging the REST API setting does not persist after saving.
Could you help us determine:
1. Why the REST API setting is not being saved on staging.
2. Where Toolset stores this configuration.
3. Whether there are known issues that cause the REST API checkbox to revert after saving.
4. How to correctly enable REST API support for existing Toolset custom post types so they are exposed through the standard WordPress REST API endpoints.
Any guidance on troubleshooting this behavior would be appreciated.
