[Resolved] Toolset types getting conflict with Content notify plugin.
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.
This is a sandbox site and you can auto-login to it using the following link:
- hidden link
And the screenshot you shared is of forum. You may try to logout once and delete all cookies and cache and try to login again to your account using your Toolset account access details.
Thanks for the support. I have informed the issue you mentioned in the previous reply to the plugin support.
Here is their reply
´So currently, I’m checking for meta-box-loader or relationship_slug in the request to see whether or not Toolset is loading.
It would be helpful if Toolset are able to provide information about a parameter that they add to each request, or when a Toolset custom field is updated, that I can check for in Content Notify to solve this moving forward.
It appears from my efforts that either of the checks I’m making, aren’t always returning correctly so it would be helpful if they can weigh on this. They’ll also have a better understanding of their plugin than I will.´
Can you please guide us what parameter is required for this issue.
Well - if Toolset custom fields are present on the add/edit post screen then you can catch it using $_POST and the custom field names created by Toolset will start will "wpcf" prefix.
Please check the following screenshot:
- hidden link
Thanks again for the support. Is it possible to provide a $_GET parameter of the toolset?
Support replied':
´The only issue is that I’m using the $_GET request as $_POST doesn’t contain the fields until much later in the saving process.
Are they able to provide a $_GET parameter for thier plugin instead?´