I see that this is working fine on https://community.nodebb.org/ , so I think something of my custom code is interfiering with the component update. I'm working on a child theme of persona theme. I've build this like 3 years ago, and constaly updating the website, but maybe something got old, not sure. I'm currently on nodebb 3.8.2

I'm working on template "chats", and my problem is that component="chat/nav-wrapper" (left sidebar with the list of chat rooms) is not beeing updated when new messages come in. The component="chat/main-wrapper" (main chat window) is owkring fine, new messages are shown as soon as the other users in the same chat room submit new messages.

I'm not sure where to look to fix this. Maybe If I see how this is done on the nodebb core files, or theme I can replicate, or try to debug better.

I can event add some custom js code that makes this feature back to work. I've been testing

socket.on('event:chats.receive', function (data) {
			console.log('------- event:chats.receive -------');
            console.log(data);
            console.log('-----------------------------------');
		});

        $(window).on('action:chat.received', function(ev, data) {
            console.log('------- action:chat.received -------');
            console.log(data);
            console.log('-----------------------------------');
          });

But these console logs only gets fired when the user is in the same room. If the user is on a different room, and gets a message, these console log are not getting not fired. I'm trying to find the right hook, so maybe I can code the code to update the component="chat/nav-wrapper" when new messages come in.

@baris thanks for the code, it worked almost perfectly. The only issue is that the code you sent only modifies the first record found. In order to modify all the records founds this is the code

db.objects.update(
  { _key: /^user:\d+:settings/ },
  { $set: { "notificationType_new-chat": "notificationemail" } },
  { multi: true } // Ensure you include this option to update multiple documents.
);

Thanks for the help!

@baris, I just found out why the chat messages weren't appearing in the digest. I've set all chat notifications for users to not send by default. If a user goes into the notification settings and changes it to email, then I see the chat notifications in the digest.

My problem now is that all users currently have this chat notification setting set to "none." How can I change all users' settings to receive notifications and emails? They can later change it back to "none" in their settings, but I need them to start receiving these notifications.

Custom script to run once? db script ? maybe a hook that I can use?

I'm not sure, but I think it is not posible to get new chat messages notifications in digest, right?

Is there some custom coding I can do with hooks, and add these type of notifications in the email digest?

when you land in the users chat url

/user/username/chats 

there are no chat opens by default, and you see a message

You have no active chats.

I want to change that, and if you land on that url, you get the latest chat open by default (this can be acchieved by opening the latest chat on that url, or redirecting to the latest chat url)

How can I get this done?

@baris Thanks. I already tested it, and this is what I was looking for.

@baris I'm working on a child theme of persona theme. I have the chat modal, and I don't want it, I want it like harmony has it, I want to click on the component="account/chat" and open the full screen "/user/username/chats/chatidnumber/" url, not sure if this component checks first if a chat room is available if not creates it.

Is there a way to remove the chat modal , and have this link to the chats page in a persona child theme?

After recoding all the static callback issues, website is working again. Thanks for the help.

I got a lot of custom plugins with that old callback function. I think that is the issue. One example is from

nodebb-plugin-cdn
I have a custom version of it (dont ask why....)

I can see that the latest update
https://github.com/NodeBB/nodebb-plugin-cdn/commit/186a98f1df60309ae4dcc4338bf6c0c15a025de3
in the exports.preLoad , they had the callback before, and in the current lastest version, that is not there anymore.

@baris thanks for the help. I'm going through all the static: hooks used in custom theme and plugins, and noticed some difference on how some of them are coded. Maybe this is the problem? some have like a next() or callback() function at the end. Can this be the issue? I see that the example you show to me doesn't have the callback / next function at the end.

example one (not calling callback)

{ "hook": "static:app.load", "method": "init" },
plugin.init = async function (data) {
	const controllers = require('./controllers');
	SocketPlugins.composer = socketMethods;

	data.router.get('/admin/plugins/composer-default', data.middleware.admin.buildHeader, controllers.renderAdminPage);
	data.router.get('/api/admin/plugins/composer-default', controllers.renderAdminPage);
};

example two (calling callback)

{ "hook": "static:app.load", "method": "init" },
exports.init = ({ router, middleware }, callback) => {
  router.get('/admin/plugins/cdn', middleware.admin.buildHeader, renderAdmin);
  router.get('/api/admin/plugins/cdn', renderAdmin);

  router.get('/api/admin/plugins/cdn/save', (req, res, next) => {
    setObject('plugin_cdn:settings', JSON.parse(req.query.settings), (err) => {
      if (err) {
        next(err);
        return;
      }

      res.sendStatus(200);
    });
  });

  callback();
};

@baris I had 3.6.5 installed, no problem. All other updates from that version up, break my website. updating to 3.6.6 works. 3.6.7 breaks my install.
upgrade does not report any problem
Build does not report any problem,
nodebb dev gets stucked

2024-05-28T13:55:23.815Z [4567/4384] - verbose: [plugins/fireHook] filter:sanitize.config
2024-05-28T13:55:23.816Z [4567/4384] - info: [plugins] Plugins OK
2024-05-28T13:55:23.816Z [4567/4384] - verbose: [plugins/fireHook] static:assets.prepare
2024-05-28T13:55:23.817Z [4567/4384] - verbose: [plugins/fireHook] static:app.preload
2024-05-28T13:55:23.817Z [4567/4384] - verbose: [plugins/fireHook] filter:router.add
2024-05-28T13:55:23.819Z [4567/4384] - verbose: [plugins/fireHook] static:app.load
2024-05-28T13:55:23.823Z [4567/4384] - verbose: [plugins/fireHook] filter:settings.get
2024-05-28T13:55:23.828Z [4567/4384] - verbose: [plugins/fireHook] filter:settings.get
-- stops here, no error, nothing, but does not work----

the nodebb updates comparison here
https://github.com/NodeBB/NodeBB/compare/v3.6.5...v3.6.7
I've noticed that if I undo the updates on src/plugins/hooks.js the nodebb starts to work again.
Any idea what can I do on my custom theme/plugins to fix it?

@julian @baris, sorry to bring you both into this discussion without much further notice. I just want to be sure about this. As of today, are there any composers in NodeBB other than the default one? Before, I remember working with Redactor and Quill, but I think those are deprecated.

@baris , @julian I have one more question about updagring composer-quill . nodebb-composer-quill like extends from nodebb-composer-default.

"modules": {
		"quill.js": "./node_modules/quill/dist/quill.js",
		"quill-magic-url.js": "./node_modules/quill-magic-url/dist/index.js",
		"quill-emoji.js": "./static/lib/emoji.js",
		"composer.js": "../nodebb-plugin-composer-default/static/lib/composer.js",
		"composer/categoryList.js": "../nodebb-plugin-composer-default/static/lib/composer/categoryList.js",
		"composer/controls.js": "../nodebb-plugin-composer-default/static/lib/composer/controls.js",
		"composer/drafts.js": "../nodebb-plugin-composer-default/static/lib/composer/drafts.js",
		"composer/formatting.js": "../nodebb-plugin-composer-default/static/lib/composer/formatting.js",
		"composer/preview.js": "../nodebb-plugin-composer-default/static/lib/composer/preview.js",
		"composer/resize.js": "../nodebb-plugin-composer-default/static/lib/composer/resize.js",
		"composer/scheduler.js": "../nodebb-plugin-composer-default/static/lib/composer/scheduler.js",
		"composer/tags.js": "../nodebb-plugin-composer-default/static/lib/composer/tags.js",
		"composer/uploads.js": "../nodebb-plugin-composer-default/static/lib/composer/uploads.js",
		"composer/autocomplete.js": "../nodebb-plugin-composer-default/static/lib/composer/autocomplete.js",
		"../admin/plugins/composer-quill.js": "./static/lib/admin.js"
	},

so, when compiling, ./nodebb build I get this error

ERROR in ./node_modules/nodebb-plugin-composer-default/static/lib/composer.js
Module not found: Error: Can't resolve 'composer/post-queue' in '...\nodebb\node_modules\nodebb-plugin-composer-default\static\lib'
Did you mean './composer/post-queue'?
Requests that should resolve in the current directory need to start with './'.
Requests that start with a name are treated as module requests and resolve within module directories (build/public/src/modules, build/public/src, node_modules, node_modules/nodebb-plugin-mentions/node_modules, node_modules/nodebb-widget-essentials/node_modules, node_modules/nodebb-rewards-essentials/node_modules, node_modules/nodebb-plugin-emoji/node_modules, node_modules/nodebb-plugin-emoji-android/node_modules, node_modules/nodebb-plugin-dbsearch/node_modules, node_modules/nodebb-plugin-community-payload/node_modules, node_modules/nodebb-plugin-greenwave-comments-api/node_modules, node_modules/nodebb-plugin-greenwave-tag-follow/node_modules, node_modules/nodebb-plugin-greenwave-update-user-api/node_modules, node_modules/nodebb-plugin-payload-api/node_modules, node_modules/nodebb-plugin-s3-uploads-updated/node_modules, node_modules/nodebb-widget-search-bar/node_modules, node_modules/nodebb-plugin-composer-quill/node_modules, node_modules/nodebb-plugin-email-helper/node_modules, node_modules/nodebb-theme-greenwave-hub/node_modules, node_modules/nodebb-plugin-composer-default/node_modules).
If changing the source code is not an option there is also a resolve options called 'preferRelative' which tries to resolve these kind of requests in the current directory too.

ERROR in ./node_modules/nodebb-plugin-composer-default/static/lib/composer/categoryList.js 100:2-111:4
Module not found: Error: Can't resolve 'composer/post-queue' in '...\nodebb\node_modules\nodebb-plugin-composer-default\static\lib\composer'

I think some of the nodebb-composer-default updates to work with nodebb v3 changed something related to the error that I just posted above. If you have an aidea what it can be, please let me know. I may be able to fix it.

On another hand, I've replaced nodebb-composer-default v10+ that is updated for nodebb v3 with the latest version of nodebb-composer-default that worked with my install (this is nodebb-plugin-composer-default v9.2.5 https://github.com/NodeBB/nodebb-plugin-composer-default/tree/v9.2.5 ) and it works, nodebb-compose-quill complies and works. But maybe I need some of the updates of nodebb-composer-default v10+, not sure. IIt would be better to have the most updated versions working. Thanks!

@The-SkyFoxx Nice!, but... is there a blocknotejs nodebb plugin already?

@baris can you give me a rough list of updates that have been made on nodebb v3 that may have broke composer - quill ? I'm trying to estimate how long it will take me to fix it for nodebb v3 (in case the composer-quill developer is not available to fix it)

So, basically I need a composer that has some wysiwyg functionallity.

I know redactor, and quill, both deprecated. Is there another option?

@baris Thanks. That fixed the problem. A couple more questions about 1-alerts, 2-composer
1 - about the alerts

in my theme im triggering some alerts like this

(function(config, app, ajaxify, $, templates) {
    'use strict';

    function changeWatching(type, tid, postion, state = 1) {
        const method = state ? 'put' : 'del';
        api[method](`/topics/${tid}/${type}`, {}, () => {
            var message = '';
            if (type === 'follow') {
                message = state ? '[[topic:following_topic.message]]' : '[[topic:not_following_topic.message]]';
            } else if (type === 'ignore') {
                message = state ? '[[topic:ignoring_topic.message]]' : '[[topic:not_following_topic.message]]';
            }

            // From here on out, type changes to 'unfollow' if state is falsy
            if (!state) {
                type = 'unfollow';
            }

            setFollowState(type, tid, postion);

            app.alert({
                alert_id: 'follow_thread',
                message: message,
                type: 'success',
                timeout: 5000,
            });

            $(window).trigger('action:topics.changeWatching', { tid: tid, type: type });
        }, () => {
            app.alert({
                type: 'danger',
                alert_id: 'topic_follow',
                title: '[[global:please_log_in]]',
                message: '[[topic:login_to_subscribe]]',
                timeout: 5000,
            });
        });

        return false;
    }


})(config, app, ajaxify, $, window.templates || null);

maybe something has changed on how alerts works on nodebb v3?

I get this error in console.

Uncaught TypeError: c.alert is not a function
at Ft.<computed>.c.alert.type (nodebb.min.js?v=356i6nfjfq9:8:17119)
at Object.<anonymous> (nodebb.min.js?v=356i6nfjfq9:9:13322)
at rt (nodebb.min.js?v=356i6nfjfq9:59:30032)
at Object.fireWith [as resolveWith] (nodebb.min.js?v=356i6nfjfq9:59:30830)
at ae (nodebb.min.js?v=356i6nfjfq9:62:6108)
at XMLHttpRequest.<anonymous>

2 - composer.
I'm using a customized version of composer-quill. In order to open up the composer modal I use this.

<a href="{relative_path}/compose" component="category/post" id="new_topic" class="gwds-btn size-lg start-discussion" data-ajaxify="false" role="button">
						<span class="label">START A DISCUSSION</span>
					</a>

when cliked on thi sbutton I get this error now

nodebb.min.js?v=356i6nfjfq9:62 Uncaught TypeError: Cannot read properties of null (reading 'querySelector')
at s.handleToggler (nodebb.min.js?v=356i6nfjfq9:62:19960)
at i.enhance (2343.a5b7580e4d0fcdbc1539.min.js:10:951)
at 2343.a5b7580e4d0fcdbc1539.min.js:10:3895

@baris these are the 2 functions that run in the renderHeader and renderFooter hooks

const env = require("./env");
const groups = require.main.require("./src/groups");
const nconf = require.main.require("nconf");
const customTags = require("./customTags");
const helper = require("./helper");
const userDigest = require.main.require("./src/user/digest");

AllPagesBuild.buildOnlyFooter = async function (hookData) {
	const req = hookData.req;
	const res = hookData.res;
	let templateValues = hookData.templateValues;
	const data = hookData.data;
	const uid = req.uid;
	const loggedIn = req.loggedIn;

	return {
		req: req,
		res: res,
		templateValues: templateValues,
		data: data,
	};
};

AllPagesBuild.build = async function (hookData) {
	const req = hookData.req;
	const res = hookData.res;
	let templateValues = hookData.templateValues;
	const data = hookData.data;

	const display_comm_hub =
		typeof nconf.get("display_comm_hub") === "undefined"
			? true
			: nconf.get("display_comm_hub");
	const GW_DS_URL = nconf.get("GW_DS_URL");

	const uid = req.uid;

	const notifications = nconf.get("show_notifications");
	const show_notifications = !!notifications;

	templateValues.loggedIn = req.loggedIn;

	templateValues.env = env;
	templateValues.env.GW_DS_URL = GW_DS_URL;
	templateValues.env.show_notifications = show_notifications;

	templateValues.customTags = customTags.tags;

	templateValues.communityGuidelinesUrl = nconf.get("communityGuidelinesUrl");

	templateValues.countryList = await helper.getAllCountriesUsed(uid);
	
	templateValues.usaStates = await helper.getAllUsStatesUsed(uid);

	//show / hide hub nav item if user belongs to administrators / farmer / pertner / staff group

	templateValues.showHubNavItem = display_comm_hub;

	return {
		req: req,
		res: res,
		templateValues: templateValues,
		data: data,
	};
};

I just removed those three, and the website starts working. So I just need to figure out how to make it work the way it was working on v2.8.12 but without those 3 hooks