Now tell me why the hell did you do that if your DOCUMENTATION SUCKS.
The forum was the ONLY WAY for developers to find solutions quickly.
You archived the entire forum without improving the documentation.
Do you realize how DUMB this is?
Literally guys... i'm astonished.
And I've been a client for many years.
And I'm a developer myself.
There is NO WAY to find ANY solution on your website without the forum.
What the hell is wrong with you?
Why should I send out a request to unfroze a topic which might even not be the one i need, when before it was publicly available and i could have solved my problem in 5 SECONDS OF GOOGLING when now it will take DAYS?
NOW TELL ME WHERE THE HELL I can find the documentation about the REST API and the answers to all my questions that were already available on the forums?
The search in this website SUCKS, being based on wordpress itself. Google was doing a pretty job at indexing.
Literally this is the DUMBEST move I've seen in a while from any company.
Now: an even more stupid question
Where in your documentation is written how to call REST API specifying the language?
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello!
1) We actually sent a mail explaining why we did this. in a nutshell, a LOT of the content there is seriously outdated and won't work anymore, which will end up crashing sites and getting unsatisfied clients because of "solutions not working".
2) You mention how our documentation sucks, but may i ask you for more constructive feedback?
- Why does it suck to you
- What would you like to see on it.
We want to improve and our documentation is an important part of this process, so your feedback is appreciated.
3) On every page there is an "unarchive" request, so you can ask for it to be unarchived and we can do so. this way we can leave the "good" forum threads and filter out the obsolete ones.
I need to access each and every custom post type via API
hidden link returns info in Italian language
How do i return the CPT press in english only?
hidden link ? hidden link ?
Is this information written anywhere in the documentation?
There is no good information for us developers in ANY of the documentation links you provided.
THe entire knowledge base was on the forum.
And now it's unaccessible.
Instead of locking it out saying "it doesn't work anymore" you guys should have taken whatever works still and factorized in a knowledge base on the website.
Instead now we have ZERO information.
Your documentation is a JOKE. If you ever written a piece of code yourself you should know it.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hi there!
1) I asked our devs and doc team to maybe improve he documentation on REST so it's completely documented (Our devs told us they are explanding REST compatibility because it's still not super complete as they'd like to and that might be a reason why we still don't have info about this)
2) hidden link ? is the correct way (so using the "lang" parameter
3) the "locked" pages is just phase one of our goal, which is to avoid old information to create trouble to clients. there are still a few things to do there and our team is working to improve it.
4) We're talking about more than 7 years of content which just can't be "selectively closed", and the content that is archived can be unarchived if requested, you just have to press a button. if you already did, please send me the link and i'll ask if it can be unarchived.
