Tell us what you are trying to do? I'm trying to get the plugins to function correctly and neither types or views perform for me like shown in your videos or documentation. I disabled all plugins and themes except 2025 and toolsets but the block functionality doesn't show fields and views show no posts in the loop. I manually created content templates using classic editor but they don't function correctly. I have completely removed several times and cleared hosting cache and disabled all local cache. I'm running on wp multisite latest version on wpmudev.
Is there any documentation that you are following? Yours
Is there a similar example that we can see?I disabled the plugins to restore the site but can reenable for you to see.
Hello. Thank you for contacting the Toolset support.
Can you please clarify that you have issue to display the custom fields you created for specific post type and those custom fields from custom field group do not display on backend post add/edit page? if yes:
Just to ensure there is no conflict with the theme/plugins you use:
Could you please try to resolve your issue by deactivating all third-party plugins as well as the default theme (switch your theme to "twentytwenty one") to check for any possible conflicts with any of the plugins or themes?
- Do you see any difference?
Thanks. The types fields seem to be affected by another plugin or the theme, they are showing up now so I will continue troubleshooting conflict. However, the Views still aren't working when created from the page method, as included in the debug. I receive "there were no posts found to display for the View's query" and noticed the content selection doesn't appear to be saving in the block editor. I was able to create a view from the dashboard and it seems to work but isn't displaying correctly in the back end editor either.
I am reporting a potential plugin vulnerability and didnt want to do it publicly. Your views and maps plugins are being blocked by nginx WAF for rules related to cross site scripting with how you are making json calls in the wp back end. This is what was breaking views and maps block creation and editing capabilities for me.
Adding these 2 exception path rules in the WAF restored functionality.
/wp-json/ToolsetBlocks/Rest/API/v1/
/wp-json/toolset-views/
I didn't see anything in your faq about this being known and am not sure how I could be the only one experiencing it.
I do not see any other reported the issue and we do not have such report even in recent times. Toolset Blocks is there since years now and there is no such vulnerability report raised here.