Skip to content
Sudonix

sudonix

Issues with v3 alpha and Harmony

Moved Solved Configure
Log in to reply

18/18

21 Jan 2023, 17:41

Did this solution help you?
Did you find the suggested solution useful? Why not buy me a coffee? It's a nice gesture, and a great way to show your appreciation 💗

Related Topics
  • undefined

    Upgrade issues

    Solved Configure
    18 13 Sept 2023, 06:58
    13 Sept 2023, 06:58
    1
    2 Votes
    2 Posts
    223 Views
    undefined
    Use this code git fetch # Grab the latest code from the NodeBB repository git checkout v3.x git reset --hard origin/v3.x And you will have the latest version without specifying it https://docs.nodebb.org/configuring/upgrade/
  • undefined

    Upgrade to NodeBB v3? 2BB or not 2BB, that is the question!

    Solved Configure
    18 27 May 2023, 09:26
    27 May 2023, 09:26
    4 Votes
    8 Posts
    507 Views
    undefined
    @Panda said in Upgrade to NodeBB v3? 2BB or not 2BB, that is the question!: So although thats a plugin it has Widget like element and stopped working on the Theme change Which is normal based on the widgets being reset when you change themes.
  • undefined

    NodeBB v3 Quick reply

    Solved Configure
    18 3 May 2023, 13:15
    3 May 2023, 13:15
    1
    2 Votes
    4 Posts
    274 Views
    undefined
    here is the link: https://app.transifex.com/nodebb/nodebb/translate/#tr
  • undefined

    NodeBB v3 Android Problem

    Solved Configure
    18 3 May 2023, 06:41
    3 May 2023, 06:41
    4 Votes
    4 Posts
    325 Views
    undefined
    thank you fixed.
  • undefined

    NodeBB: Favicon upload issue

    Solved Configure
    18 4 Apr 2023, 10:58
    4 Apr 2023, 10:58
    1
    3 Votes
    12 Posts
    602 Views
    undefined
    @phenomlab I am on a Mac, so I used the “Option + Command + I”, and then performed the steps. It loaded my favicon! I checked on Firefox which I haven’t used before, and it showed my favicon also! That’s fantastic and thank you for the help!
  • undefined

    NodeBB: Upgrading to NodeBB v3.x

    Solved Configure
    18 1 Apr 2023, 10:33
    1 Apr 2023, 10:33
    0 Votes
    6 Posts
    368 Views
    undefined
    @mventures You’d need to connect to the server and execute it directly - not on your local terminal. Review the guide below, which will show you how to gain access via SSH to your server https://docs.ovh.com/gb/en/dedicated/ssh-introduction/ Once you have access, you’ll need to navigate to the actual folder where NodeBB is installed You’ll then need to change to the directory as shown below /home/unbuntu/nodebb [image: 1680448167972-fdffe673-bf63-4b6d-a728-5506fddc1aff-image.png] In most cases, initial access takes you to the root of the file system. You can always issue pwd in a Linux terminal which will show you the Present Working Directory. From there, you can issue the command cd /home/ubuntu/nodebb Once in the NodeBB directory, you’d use the below commands ./nodebb stop git fetch && git checkout develop && git reset --hard origin/develop ./nodebb upgrade ./nodebb start Line 1 stops the NodeBB instance Line 2 gets the latest files from GIT (repository) and then checks out the development branch. It then resets the version you are using to the development branch ready for v3 Line 3 Runs the upgrade once the new branch is set, and code pulled Line 4 Restarts the NodeBB instance after the upgrade has completed Note that when you restart NodeBB and log back in, things will look very different to what you had in v2.
  • undefined

    NodeBB Global Tchat : Forum with many users performance issues

    Solved Configure
    18 6 Jan 2023, 14:23
    6 Jan 2023, 14:23
    1
    5 Votes
    13 Posts
    737 Views
    undefined
    'use strict'; const winston = require('winston'); const user = require('../user'); const notifications = require('../notifications'); const sockets = require('../socket.io'); const plugins = require('../plugins'); const meta = require('../meta'); module.exports = function (Messaging) { Messaging.notifyQueue = {}; // Only used to notify a user of a new chat message, see Messaging.notifyUser Messaging.notifyUsersInRoom = async (fromUid, roomId, messageObj) => { let uids = await Messaging.getUidsInRoom(roomId, 0, -1); uids = await user.blocks.filterUids(fromUid, uids); let data = { roomId: roomId, fromUid: fromUid, message: messageObj, uids: uids, }; data = await plugins.hooks.fire('filter:messaging.notify', data); if (!data || !data.uids || !data.uids.length) { return; } uids = data.uids; uids.forEach((uid) => { data.self = parseInt(uid, 10) === parseInt(fromUid, 10) ? 1 : 0; Messaging.pushUnreadCount(uid); sockets.in(`uid_${uid}`).emit('event:chats.receive', data); }); if (messageObj.system) { return; } // Delayed notifications let queueObj = Messaging.notifyQueue[`${fromUid}:${roomId}`]; if (queueObj) { queueObj.message.content += `\n${messageObj.content}`; clearTimeout(queueObj.timeout); } else { queueObj = { message: messageObj, }; Messaging.notifyQueue[`${fromUid}:${roomId}`] = queueObj; } queueObj.timeout = setTimeout(async () => { try { await sendNotifications(fromUid, uids, roomId, queueObj.message); } catch (err) { winston.error(`[messaging/notifications] Unabled to send notification\n${err.stack}`); } }, meta.config.notificationSendDelay * 1000); }; async function sendNotifications(fromuid, uids, roomId, messageObj) { const isOnline = await user.isOnline(uids); uids = uids.filter((uid, index) => !isOnline[index] && parseInt(fromuid, 10) !== parseInt(uid, 10)); if (!uids.length) { return; } if (roomId != 11) { // 5 Is the ID of the ID of the global chat room. Messaging.getUidsInRoom(roomId, 0, -1); // Proceed as normal. } else { user.getUidsFromSet('users:online', 0, -1); // Only notify online users. } const { displayname } = messageObj.fromUser; const isGroupChat = await Messaging.isGroupChat(roomId); const notification = await notifications.create({ type: isGroupChat ? 'new-group-chat' : 'new-chat', subject: `[[email:notif.chat.subject, ${displayname}]]`, bodyShort: `[[notifications:new_message_from, ${displayname}]]`, bodyLong: messageObj.content, nid: `chat_${fromuid}_${roomId}`, from: fromuid, path: `/chats/${messageObj.roomId}`, }); delete Messaging.notifyQueue[`${fromuid}:${roomId}`]; notifications.push(notification, uids); } };
  • Hariundefined

    Issues getting Flarum to work on new host

    Solved Configure
    18 16 Feb 2022, 12:08
    16 Feb 2022, 12:08
    14 Votes
    65 Posts
    6k Views
    undefined
    @crazycells huh. Thanks. Will need to check that as well.