@baris: MAXON with his PluginCafé discussion board for Cinema 4D plugins external developers.

Cheers, KK

Hi community first and foremost thank for your valuable support.

I need to retrieve custom data I've written to mongoDB and I'd like them to be returned as JSON string via a custom WriteAPI-enabled route.

A few notes to give a better context:

• I'm currently on Ubuntu 18 / nodebb 1.16.2 / Mongo DB 4.0.22 / npm 6.14.10

• I've already read

  • extends nodebb write-api?
  • Extending routes into the write api plugin

• I've looked at

  • nodebb-plugin-friends on GitHub
  • WriteAPI doc
  • ReadAPI doc

• and, in the end, I've created an API Access token bound to the forum administrator which works nicely to read and write in the forum (e.g. retrieving the topics or creating a new one)

Issues:

• Upon installing nodebb-plugin-friends (clone and npm link) and activating in a pristine test forum I can see the hook in Advanced -> Hooks but:
  • why looking at the nodebb log (run as ./nodebb dev) I can't see [plugins/friends] Write API integration enabled, routes added. as specified here?
  • assuming I'm using Postman for testing purposes how should i reach these routes? (none of these - <url/to/nodebb>/api/v3/friends/:uid, <url/to/nodebb>/api/friends/:uid, <url/to/nodebb>/friends/:uid, <url/to/nodebb>api/v3/plugins/friends/:uid - worked for me)
• Upon creating a test plugin (see below library.js and plugin.json) I'm not able to reach any of the established new routes (as much as reported above): how can I debug the issue? Log is silent and

library.js

'use strict';

(function(routes) {

  routes.initWriteRoutes = function(data, callback) {

    data.router.get('/route1', data.apiMiddleware.requireUser, data.apiMiddleware.requireAdmin, middleware.verifyUserExists, function(req, res) {
      console.log("/route1 reached via get");
      res.sendStatus(200);
    });

    data.router.post('/route2', data.apiMiddleware.requireUser, middleware.verifyUserExists, function(req, res) {
      console.log("/route2 reached via post");
      res.sendStatus(200);
    });

    data.router.delete('/route3', data.apiMiddleware.requireUser, middleware.verifyUserExists, function(req, res) {
      console.log("/route3 reached via delete");
      res.sendStatus(200);
    });

    console.log('[plugins/test] Write API integration enabled, routes added.');
    callback(null, data);
  };

}(module.exports));

plugin.json

{
  "library": "./library.js",
  "hooks": [
      { "hook": "filter:plugin.write-api.routes", "method": "initWriteRoutes" }
  ]
}

• assuming nodebb-plugin-friends is installed why the log reports info: [api] Adding 0 route(s) to 'api/v3/plugins' with 0 new routes? Shouldn't it include at least the new routes coming with this plugin?

I apologise for the length of this post, but I think this might help you to steer me in the right direction.

Best, Riccardo

Hi community,

is it possible to specify multiple tags in the Tags page or to even define boolean expression with (AND, OR, NOT)?

Best, KK

@julian that's awesome thanks a lot!

@pitaj here you are

https://github.com/NodeBB/NodeBB/issues/9503

rgigante created this issue in NodeBB/NodeBB

closed Failed to delete a user if user has started a chat #9503

Hi Community,

I'm in the process of preparing a forum for the go-live and I want to cleanup all the users that tested it.
This is easy as long as a user didn't engaged with the chat otherwise when I try to delete such user and his contents the deletion process breaks and the user becomes a zombie user (basically that disappears from the users list but remains attached to the group he was assigned and there are still track of him on the DB)

The log shows:

2021-04-23T14:05:53.452Z [4567/1009599] - verbose: [plugins/fireHook] filter:privileges:isUserAllowedTo
2021-04-23T14:05:53.453Z [4567/1009599] - verbose: [plugins/fireHook] filter:privileges:isAllowedTo
2021-04-23T14:05:53.455Z [4567/1009599] - verbose: [plugins/fireHook] filter:user.whitelistFields
2021-04-23T14:05:53.456Z [4567/1009599] - verbose: [plugins/fireHook] filter:user.getFields
2021-04-23T14:05:53.458Z [4567/1009599] - verbose: [plugins/fireHook] filter:users.get
2021-04-23T14:05:53.468Z [4567/1009599] - verbose: [plugins/fireHook] static:user.delete
2021-04-23T14:05:53.470Z [4567/1009599] - verbose: [plugins/fireHook] filter:user.whitelistFields
2021-04-23T14:05:53.471Z [4567/1009599] - verbose: [plugins/fireHook] filter:user.getFields
2021-04-23T14:05:53.472Z [4567/1009599] - verbose: [plugins/fireHook] filter:users.get
2021-04-23T14:05:53.482Z [4567/1009599] - verbose: [plugins/fireHook] filter:messaging.isUserInRoom
2021-04-23T14:05:53.491Z [4567/1009599] - verbose: [plugins/fireHook] filter:messaging.save
[api] Exception caught, error with stack trace follows:
Error: [[error:chat-room-does-not-exist]]
    at Messaging.markUnread (/home/nodebb/backstage_prod/src/messaging/unread.js:34:10)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async Promise.all (index 2)
    at async Messaging.addMessage (/home/nodebb/backstage_prod/src/messaging/create.js:58:3)
    at async Messaging.addSystemMessage (/home/nodebb/backstage_prod/src/messaging/create.js:77:19)
    at async Promise.all (index 1)
    at async Messaging.leaveRooms (/home/nodebb/backstage_prod/src/messaging/rooms.js:151:3)
    at async Promise.all (index 0)
    at async deleteChats (/home/nodebb/backstage_prod/src/user/delete.js:177:3)

I'm currently on 1.16.2 and this looks to me like a bug.
Do you have any idea on how I should clean-up the chat data of these users and then safely operate a "delete user and contents"?

Cheers, Riccardo

Hi Community,

I've recently upgraded from 1.12.x to 1.16.x and I've done it first on a testing environment and, upon success, on production environment.

Today, after a few days from the upgrade, I've realized that on the production instance the list of categories from category-drop down menu, is completely missing either on front-end (typical case when you want to move a thread) and on back-end (typical case when you want to set privileges).

Production instance(left) Vs Test instance (Right)

I've no clue what could be the case and how to get it fixed.

Thanks, Riccardo

@baris thanks a lot for the input.
The issue was independent by the theme (slick was 1.3.8) but it seems that removing the height: 100% has fixed the issue.

If it gets back I'll let you know.

For the time being, thanks a lot!

@baris feel free to test on plugincafe.maxon.net

Hi all,

I've just updated 1.12.x to 1.16.x and it seems that infinite scrolling has issues when, after having scrolled down a bit, either you can't scroll down further or getting back to the top the scrolling doesn't let go up to the very first post.

It has also been reported by some users some weird "infinite flickering" mechanism when scrolling up. (unfortunately it seems I can't upload gif to show the issue)

I'm running 1.16.2 with slick theme. Are you aware of this issues? Is there anything to mitigate the issue ? Can it be something related to nginx configuration?

Thanks, Riccardo

@julian thanks for the update.

I'm facing and issue and I dunno if it a know limitation.
Is it possible to have to plugin showing Solved/Unsolved labels correctly with the Slick Theme when browsing categories? The labels only appear when a thread is selected.

Cheers, R

@baris thanks a lot! You brought me into the right direction.

I've queried the DB for db.getCollection('objects').find({"_key":{$regex:'maxonIDId:uid'}}) and deleted the found object. This just made the trick and disconnected the retuned OAuthID from the actual nodebb uid.

Thanks a lot for looking at the thread and also checking the my code!

Really appreciated you're awesome guys!

Looking at one of the sessions object I've spotted
"registration\":{\"returnTo\":\"/\",\"uid\":8},\"passport\":{\"user\":8}}"

which seems like it's referring to the same uid that my user had before getting deleted. Looks like that re-registering myself with the same account tries to use the same uid.

Does it make any sense to you gurus?

Cheers, R

@pitaj already done and sadly no better results