I unterstand and value your feedback, and thank you for the Trust you put in Toolset Technologies.
Regarding YOAST integration, Toolset does not and never did officially provide a Support or Integration for it.
As you see, all older threads provide the modified (with the wpcf-prefixes) YOAST function which they suggest to add, so to make things work with YOAST.
Now they decided to deprecate this API.
Since we do not provide this in our Tools natively, I don't agree that we should update something that is not existent in our Tools, or provide some sort of Updated Custom Code to make things work.
Of course I agree that it would be nice have this natively, or at least Documentation that explains how to make things work with Toolset and YOAST.
Ans as such you can consider this request as filed.
Regarding "being behind" different updates such as PHP7, WordPress and other, I agree onto topic of PHP7
Despite the early request (filed by me) the Toolset was not ready for PHP 7 in time, mainly due to the wrong assumption, it would take longer for PHP7 to be released.
What is to consider, PHP7 is not (in most cases) even used on specially shared servers, and usually only VPN solutions allow you to use it.
Not a excuse, just a thing to notice.
Regarding WordPress 4.5 we did not have any issues I know if, that where due to neglected API Changes on our side.
All I know of was due to the user either not updating WordPress but updating Toolset, or vice versa, or having Outdated OS and Browsers.
I recall - and want to mention, a huge catastrophe in the Toolset World which was WordPress API Update for ShortCodes version 4.2.3
In that case, WordPress notified nobody, and pushed the changes in less then 24 hours before release.
Toolset solve the class in less then a Week, including Weekend.
With this in mind - I think it is visible that Toolset does everything possible to satisfy the User's needs and reacts, when needed. And usually, we are up to date with specially WordPress.
Please don't understand me wrong. As you gave me honest feedback, which I highly appreciate, I want to respect this by providing you honest feedback as well, not excusing or apologizing issues that are not to excuse or apologize, and also determining what Toolset does and what not.
I also agree on your concern that "more features produce more bugs"
But the, our Features come from requests. We don't invent them.
It's usually a high load of requests by users, that make us implement something, and this also produces satisfaction.
Of course, you are absolutely right that a minimal set is better to control, but then I would need to ask... is It appropriate to support a integration with YOAST, which is also a new feature?
Of curse it is, but it also gives room for failure.
So it is a give and take situation.
We try to do our Best, and provide a affordable Plugin with many grease features and a professional Support, which is, in other Plugins, either more expensive or not available.
Regarding BuddyPress, we still have some Cells (hidden) in Layouts, but it has been not developed actively and it's not currently planned to do so.
It is mainly due to the fact that those templates are hardcoded and we can not dynamically control them.
If you are interested in what we provide for BuddyPress, you can read more here:
https://toolset.com/forums/topic/buddypress-pages-not-using-layouts/
https://toolset.com/forums/topic/buddypressbbpress-layout/
https://toolset.com/forums/topic/buddypress-and-bbpress-integration/
I, to conclude, filed a request to enable some support for YOAST, or to provide a DOC on the "how-to" for the new YOAST integration method.
For now, this is considered Custom Code and a new feature to implement.
For your information, also PODS (example) is not integrating YOAST natively.
And in the comments here:
hidden link
it is very visible, neither YOAST or any 3rd party app actually provides solutions out of the box here.
Thank you for understanding.