Plugin Development

having the same problem, any luck?

@fahx00s if your other server is using oauth2, then use sso-oauth2-multiple plugin

Perfect! Does the job super elegantly thank you

You should be able to overwrite a core module completely using your plugins modules section. For example to overwrite the navigator module with your own you can do. "modules": { "navigator": "public/navigator.js" }, Copy the navigator module from core and make your changes and it will replace the core module during build.

This commit implements that, the teasers are updated in the event event:unread.updateChatCount because that is sent even if the user is not currently in that room. https://github.com/NodeBB/NodeBB/commit/ac644ac2866bfa48a939a94b6ec34ad9fd493f7d

You can also use db.objects.updateMany

You could use the below custom javascript, it will open the last chat if there is no open chat. $(window).on('action:ajaxify.end', async () => { const { data } = ajaxify; if (data.template.chats && !data.template.roomId && data.rooms.length) { const Chats = await app.require('forum/chats'); Chats.switchChat(data.rooms[0].roomId); } });

What is the name of the plugin? Does it start with nodebb-plugin-?

I ended up adding a child span to hold the tooltip, and just removing the child altogether anytime the event fired. Inserting a new element and then setting the tooltip was the only way to get the tooltip updated correctly (for me). Thanks for the help!

A socket event is sent when a new topic or reply is made, they are called event:new_topic and event:new_post. We listen to that and update the ui when a new reply comes in.

@יושב-אוהלים Hi, I would appreciate it if you could write how it can be done

Depending on what you want to change, you can modify it via css or override the bootbox.dialog method like we do in core https://github.com/NodeBB/NodeBB/blob/master/public/vendor/bootbox/wrapper.js#L27-L45

Try navigating to the route created by the plugin for the admin page, it should be something like /admin/plugins/pluginname. If that is giving a 404 that means your plugin isn't being loaded properly on startup. Check nodebb logs for any errors / warnings. The quick start plugin creates a route at /admin/plugins/quickstart https://github.com/NodeBB/nodebb-plugin-quickstart/blob/master/library.js#L37

@baris Just found the root cause of the weird behaviour! Turns out that there is a bug in my NodeBB dev startup scripts. One of the steps involves automatically symlink plugin packages for a more seamless plugin development. The issue happens when the yarn link only happens after NodeBB build but before NodeBB start Thus there is this weird behaviour of the plugin is loaded but its public assets are not built 🫠 Thank you for your pointers and help

After a lot tries here and there I have reached the cause of this issue... I cause is some plugins which are not running properly. It is due to this it hinders the compilation of client side JS for all the plugin which loads after that.

Yeah your flow should work, we don't trigger it on all instances as that would cause issues if the function is doing db writes for example. You would have 2+ instances trying to create the same records etc.

My fault. I wasn't calling ajaxify.go correctly. All works now.

I would advise against using those since they operate on fields that are not indexed. If all you want to store is a uid and score pair you can use sorted sets like below. //setting values await db.sortedSetAdd('pluginname:users:customstats', [score1, score2], [uid1, uid2]); // getting first 10 values await db.getSortedSetRevRange('pluginname:users:customstats', 0, 9);

I don't know why, but taking those conditionals checks that I have to the route controller fixed the problem. I don't need to reload the page anymore.