We are attempting to package our toolset based theme and settings for distributing a project to a client, without allowing them editing access to the views, layouts, etc - this was previously possible using Toolset Embedded. The Packager plugin typically used to prep deployments doesn't look to be present on your website or through wp-admin anymore and we were wondering if they were discontinued or if there is just a newer process in place for distributing Toolset based themes and websites to clients.
Toolset-based themes are in something of a hiatus at the moment—it requires considerable work to update to be able to work with Blocks and as the feature was taken up by only a small number of clients it is hard to justify.
I'll need to get confirmation of an official position, and speak to the documentation team about posting that on the old documentation page which appears to have been retired.
One thing I'm struggling to understand, though, is how you have been able to use this, as you have a Lifetime account and Toolset-based Themes required a Pro Author account. Has your account changed, or you were collaborating with someone with a different account type?
Sorry to hear about the hiatus. When we started using Toolset, back in 2016, the big selling point for us was the ability to create custom Toolset-based child themes we could then package and license to our clients. We were so impressed with the Toolset framework that we purchased your highest-priced package, the Lifetime license, and incorporated it into our core strategy for deploying custom WordPress solutions. Furthermore, we've been a Toolset Contractor since 2017.
The packaging/embedding feature is key as it allows us to distribute to clients while minimizing the risk our work can be copied over to other sites in violation of their license.
Admittedly we haven't had to do this for some time, however, it is still a feature we are highly interested in and has become a keystone in our strategy for some time now. When we went to do it recently we used a previous version that we had been using prior, however, this time it did not work. That's when we realized the documentation and plugins were no longer on your site and filed the ticket.
We should also note that we have been only using legacy versions of the downloads as we do not currently use Blocks (we use visual composers for our client builds).
Hopefully, you can help us out as you have in the past. We are still highly interested in building Toolset-based custom themes for deployments and would really like to be able to take the proper steps to protect our work and prevent unauthorized versions from being distributed. We are more than willing to work with you on this, as we have on other tickets we've filed over the years, (many of which you've personally responded to,) some of which have ended up becoming forum topics and helped you identify and fix bugs in your releases and provide fixes for other Toolset users. We can certainly understand, however, that you may not remember as you have worked with many like us while we have only worked with a precious few of you.