yeah im having the same EADDRINUSE error when trying to run NodBB in debugger mode (WebStorm)

I would love a solution or a workaround because I've been trying for a couple days to try and get this working. I just want to be able to debug NodeBB's plugins and core components

PS. I've tried WebStorm, node-inspector and strong-cli. I've tried them all with latest node.js and also version 0.10

would it be possible to create a plugin that allows a user to send another user an attachment (zip, pdf, doc etc..) through the chat? If anybody could point me in the right direction that would be awesome! thanks

@yariplus that's awesome..! any pointers on how you did it?

Hi,
I was wondering if anyone has successfully integrated NodeBB into their own web application?

See, I have an web application that works online and offline. Users login to the application and do stuff. What I'm missing in this application is a 'Home' screen. I was thinking of using NodeBB as the 'Home" screen and also benefiting from all the features that NodeBB provides, like Instant Messaging for example. I would also like for my existing application to be able to act on hooks that NodeBB fires. But I'm not sure how the integration of NodeBB with an existing application would work? Or if anything like this would be possible?

Thanks,
Armando

Hi everyone,
So, I'm able to write a plugin that can create a topic in a certain category whenever NodeBB fires a particular hook, using this:

var Topics = require('../../src/topics');

Topics.post({
    uid: 1,
    title: 'this is a title',
    content: 'this is the content of the message', 
    cid: 27}, 
function (err, result) {
    if (!err) {
        console.log("successfully created topic.");
    }
});

I was wondering if there is a way to have this particular block of code in a seperate javascript file and whenever that file is executed have it create the topic?

finally got it working!! thanks @esiao couldn't have done it without you..!
I changed 'Chat' index.html to look like this"

<script src="http://127.0.0.1:4567/socket.io/socket.io.js"></script>
<script>
    var socket = io.connect('http://127.0.0.1:4567');
    socket.emit('topics.test', {data: "some data"}, function(err, result) {
        alert(result);
    });
</script>

I removed the line that I added to NodeBB's /src/socketio/index.js

And used @Schamper post from here where he explains how to use websockets in your plugins. So thanks @Schamper for the post it helped a lot..!

nvm, I got it working. I was confused how async.each() worked..!

here's what I ended up with:

                function getMainPost(topics, callback) {
                    posts.getPostFields(topics.mainPid, ["content"], function (err, data) {
                        topics.content = data.content;
                        callback(null);
                    });

                }

            function getRecentTopics(category, callback) {
                categories.getCategoryTopics(category.cid, 0, parseInt(category.numRecentReplies, 10), uid, function (err, data) {
                    var topics = data.topics;
                    category.topics = topics;
                    category.topic_count = topics.length;

                    async.each(topics, getMainPost, function (err) {
                        callback(null);
                    });

                });
            }

            async.each(categoryData, getRecentTopics, function (err) {
                next(err, categoryData);
            });

@Kowlin yeah hopefully! I'm actually gonna take another stab at it right now and will update if I make some progress

@pidjab thanks! will work with that

@pitaj said:

IE iframe csrf error

Awesome! that fixed it! I swear I googled it, but I must've overlooked that particular answer! Thanks again @pitaj

@julian @pitaj any ideas on how to get around it?

@julian yeah only through iFrame

the request headers look fine, it has x-csrf-token and Cookie (express.side=...)

Hi,

When I open NodeBB through an iFrame using IE 11 and attempt to login, im presented with an "invalid csrf token" error and login fails. But when I try it with Google Chrome, everything works as expected. Anybody have an idea why that is?

PS. I tested on a fresh IE (reseted ALL my settings, including cookies, etc.)

Thanks,
Armando

@pitaj nice..! all the topics by tag for a particular category?

@pitaj oh ok, I'll see if I have some time tomorrow so i can give it another shot but anyways good luck!

nvm, just figured out that it is normal, it literally says so in a comment

https://github.com/NodeBB/NodeBB/blob/a054353b6c9896693bfb9c64e7e389380bff1ea1/public/src/sockets.js#L25

Hi,

I noticed that if i lose connection to NodeBB my socket attempts to reconnect more times than what I have set in my settings (5 times). It tries to reconnect 5 times with a delay of 1500 between each reconnect attempt then it sits idle for like 10 seconds and then it starts all over again. Is this normal?

Thanks,
Armando

@pitaj any luck..?

tried, but couldn't find a way to make it work correctly.. whatever i tried would break the 'load more as you scroll' feature.