To keep content in the forums more current posts older than 5 years have been deleted, and posts older than 2 years have been deleted.
If you are arriving at these links via Google it will probably take a few weeks for the links to disappear from the Google index.
At the moment if you arrive at an archived post it will show a 404, but we have an update to our system coming soon where this will be replaced with an explanatory note and a button to request unarchiving a particular thread.
In the meantime, do you have a specific question we can help you with?
Oh my, that is horrible... you guys really want us developers to suffer? First, the useless blocks "editing" and now this. I can't even explain how badly this hurts. My team references all those old posts every single work day. Your API is so good and convenient I can't believe you guys don't see the value in supporting it. I get that you are "no PHP" but why don't you value your API? It's better than what ACF offers. Anyways I digress. Please ask your manager to consider not making us suffer like this and let me know what they say.
In the meantime, I'll be submitting requests for help on 100's of questions that have already been answered. And without the older support tickets, it's going to even be hard for me to know exactly what to ask. This is scarrrryyyy.
Unfortunately there isn't much we can do about this. The most we can do is to unarchive some of the threads between 2-4 years old when requested.
We will have to essentially revisit the issues when they come up in the forum and provide an up to date solution that reflects how Toolset currently is rather than relying on the old methods because functions and hooks may have changed or removed during subsequent updates of our plugins.
You guys have totally crippled me by taking away all of the documentation. How many people are actually using toolset legacy views and the API? Am I going to have to rebuild the entire database of knowledge by myself? I really need to know because with all of this extra work and inability to work efficiently I need to weigh moving our entire team over to Advanced Custom Fields because they don't hide their documentation and the learning curve to move over there may be less than work than rebuilding your database of answers that already exist.
Thank you for all your help but I can't afford to wait on replies from your team every day for the next 5-6 months while I rebuild your database of questions that have already been answered. If there are a ton of other people helping me ask all the questions that have already been answered then it will make my job a lot easier. But if I'm going to be one of the only people asking it's too big of a task for me.
-Best Regards and thank you for helping make this very critical decision for our company.
Thank God, I really did not want to move over to ACF if I didn't have to. I hope your team continues to value your API you could really gain a lot of new members if developers like me knew how many benefits and time savings it provides over ACF.
I will do my best to report any old threads I see that are outdated and submit new tickets to give a better new answer. Maybe you guys can shut them down one by one like that with all of our help overtime.
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.
