Skip Navigation

[Resolved] Request for information on Toolset roadmap and mid-term support

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.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Kolkata (GMT+05:30)

This topic contains 1 reply, has 1 voice.

Last updated by Minesh 1 week, 1 day ago.

Assisted by: Minesh.

Author
Posts
#2843140

Good morning,

we are contacting you to request an official clarification regarding the continuity, maintenance, and support of Toolset in the mid term.

We are currently developing a structured, data-driven project based on Toolset (custom post types, custom fields, relationships, Views, maps, and tables). The project is already in production and has been planned with an expected operational lifespan of at least 5–6 years, with the possibility of further extension.

We would also like to take this opportunity to say that we are very satisfied with Toolset. We consider it a solid solution well suited for complex projects and, for this reason, we are evaluating its adoption for additional future projects as well. To make this decision confidently, it is important for us to have a clear understanding of the product’s long-term continuity.

Before proceeding further with development and consolidating the architecture, we would appreciate clarification on the following points:
1. Toolset roadmap
Is the continued development and support of Toolset planned for the mid term (5–6 years)?
2. Compatibility with future versions of WordPress and PHP
Will Toolset continue to be maintained and kept compatible with upcoming WordPress and PHP versions over the next several years?
3. Stability of the current architecture
Are the core features (fields, relationships, Views, maps, queries) considered stable and expected to remain supported over time, without requiring forced migrations to other systems?
4. End-of-life policy
In the event of future ecosystem changes, is a gradual and well-communicated approach planned, allowing existing projects to continue operating without critical impact?

For us, it is essential to rely on a solid and well-maintained technological foundation, consistent with projects that are not short-lived but designed to last for many years.

We look forward to your response and thank you in advance for your availability.

#2843172

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

There is no plan to stop Toolset support or developement in as of now.

The thing is that - with the release of Toolset Blocks we shifted the focus in support of working with the native WordPress block editor instead of providing and maintaining support for a different page builders like (Divi Builder, WP Bakery page Builder, Beaver Builder) , and for now, that will continue to be the case.

We don't expect to do specialised work to integrate with any of the page builders with Toolset thats the key difference otherwise if you want to build anything with Toolset it should be keep working and supported.

In addition to that - I would like to tell you that plugin updates are around the corner. I do not have exact date but you can expect it by this month end or by Feb-march probabally.

Please keep your eye on our blog.
- https://toolset.com/blog/

1. Toolset roadmap
Is the continued development and support of Toolset planned for the mid term (5–6 years)?
===>
You can definately consider Toolset and contact Toolset Support as required.

2. Compatibility with future versions of WordPress and PHP
Will Toolset continue to be maintained and kept compatible with upcoming WordPress and PHP versions over the next several years?
===>
By the time we will be adding the compatibiliy for PHP and WordPress version as required.

3. Stability of the current architecture
Are the core features (fields, relationships, Views, maps, queries) considered stable and expected to remain supported over time, without requiring forced migrations to other systems?
==>
Toolset offers Block based support using which you can create (Views, Content Templates, Archives) and legacy views both will be remain supported and there are still people (users) who are much more confortable using legacy views as they can extend the output of views/content templates/archive as required.

4. End-of-life policy
In the event of future ecosystem changes, is a gradual and well-communicated approach planned, allowing existing projects to continue operating without critical impact?
===>
Yes, we will informed you well in advance if there is anything relly important regarding the development,support or event payment plans changes and we will try to be as transparant as we can and make sure sites build on top using Toolset keep running without any issue.

I would like to express "thank you" in order to keep confidance in Toolset and its capabilities and I hope users like to will keep it alive and share positive feedback.