Category Follow/Unfollow
-
@julian, thanks for the update.
"The other issue is that the top of the docs always says "3.0.0", which isn't quite correct. It's hardcoded currently."
This will be the dot above the I to make it more correct; in this case, I assume, 3.5.1.I have deployed a version from the "develop" branch, which states 3.5.1 in the administration dashboard.
Shouldn't this also state something differently to make it differ from the production branches?I'm still getting a 404 error with the watch API endpoint in this case:
"https://nodebb.dangdi.life/api/v3/categories/2/watch"
with the body:
{
"uid": 2,
"state": "watching"
}Should I run a different branch?
-
@Mikkel-Lindhard how are you making the requests, the watch routes are definitely on the
develop
branch. https://github.com/NodeBB/NodeBB/blob/develop/src/routes/write/categories.js#L24-L25. You need to make aput
request to/api/v3/categories/2/watch
-
@baris Through Postman - I can share the request if you have the time; otherwise, here is a screenshot of the Postman configuration:
-
Yields 404 also.
Can I, in the administration Dashboard, see if I'm running on the "develop" branch?
From serverside, I can check with git status where it clearly states I'm running on that branch but from the dashboard. -
endpoints are present:
setupApiRoute(router, 'put', '/:cid/watch', [...middlewares, middleware.assert.category], controllers.write.categories.setWat> setupApiRoute(router, 'delete', '/:cid/watch', [...middlewares, middleware.assert.category], controllers.write.categories.set>
-
@baris I have it working - I just needed to use a user token that was not the master and add the _uid=0 to as param..
-
It was indeed not necessary to have the _uid.