this is a follow-up to this support thread:
https://toolset.com/forums/topic/use-toolset-in-plugin/
wouldn't it be a great feature if
- Toolset could be used in backend (may very well be limited function set)
- Could be packaged in a plugin
?
from a technical standpoint i don't see a show-stopper. the biggest one would probably be that plugin & theme can have toolset, but this should be managable?
it would be a great help for developing the backend part of a plugin, also making it easy to separate form from function. it would be marvellous to have the datastructure and design of a plugin separated from the code like that. plus, the whole frontend part!
i haven't found a platform that can do this (if you know of one, please, do let me know ). this would be an absolute killer-feature!
Well, Toolset is a Plugin that does a few things, by far not enough to build a Plugin on it, unless the Plugin you'd build does more or less what Toolset does already, which we can use as a plugin already.
We have had similar requests in past but we did never work in that direction as the focus of Toolset is to let users build Websites with WordPress without using code.
The main features focused on are access control, data manipulation and display + search and layouting.
Building plugins requires other kind of software that lets you create new logic - not mask the same logic in a new design.
This plugin here is probably the most advanced in that section:
hidden link
Toolset Plugins could always be required in another plugin (WordPress offers methods to require other plugins on install: https://wordpress.stackexchange.com/questions/127818/how-to-make-a-plugin-require-another-plugin), or bundled with a Theme, achieving the same result as bundling it in a Plugin.
Related to the "Use Toolset in the backend" - we will not develop in that direction but it's theoretically possible anyway, using our API.
Having a custom plugin that puts certain data into the backend which is created or else controlled by Toolset, is possible.
You'd need to create or manage your content with Toolset as used to, and then put the things where you want them, by calling them in your custom plugins code with the API's:
https://toolset.com/documentation/#programmer-information
https://toolset.com/documentation/programmer-reference/
However I would only see a sense in this for example displaying a View in the backend that lets me see some content.
It is as well not the goal of Toolset and is not something we test or support officially.
What is the reason that you cannot ship Toolset using either a requirement in your custom plugin or bundled with the Theme?
Hi Beda
Thanks for the concise answer!
Yes, i guess it would add more complexity than solving problems.
Kind regards
Beat
