@JaredBusch said:
A quick
firewall-cmd --zone=public --add-port=4567/tcp --permanentandfirewall-cmd --reloadlater
And there we go.
Thanks @rbeer for the information about nodejs versions. I did not see the indicator that you did obviously.
Very nice! Glad to see it working now. 
And, don't you worry! I was tearing my hair out for about an hour, when I stumbled upon that error some weeks ago. 
@xen
Binding a port through your ssh connection is actually quite simple.
(The following assumes that you are using the OpenSSH client on GNU/Linux)
tl;dr:
https://youtu.be/vC7Smc67gPg
ssh user@remotehost.com -L 7000:localhost:6379-L ... with the syntax:
7000 to the remotes localhost interface on (redis-) port 6379, you can create a new connection in Redis Desktop Manager, ignoring the SSH tab in the "New Connection" dialog and simply connecting to localhost:7000.
That might be true. I am not familiar with CentOS and its package management.
Replacing the install instructions in question with nodesource (https://github.com/nodesource/distributions/tree/master/), might be a good idea. I know e.g. that Debian also has 0.10.x in its repos.
All your logs and screenshots show a nodejs version 0.10.x. That's heavily outdated. Which manifests itself fataly in
../node_modules/nan/nan.h:328:47: error: ‘REPLACE_INVALID_UTF8’ is not a member of ‘v8::String’
static const unsigned kReplaceInvalidUtf8 = v8::String::REPLACE_INVALID_UTF8;
i.e. a module, that needs compilation, can't find a member (REPLACE_INVALID_UTF8) of the String class in v8. It must have been introduced later. Upgrading to 0.12.x at least should solve this problem.
@rbeer said:
I'm curious about the contents of two files:
- /var/log/redis/redis-server.log
- /path/to/nodebb/log/nodebb.log
Hi @Pilvinen
I hope you didn't purge redis, already. That could have deleted the log file, as well.
I'm curious about the contents of two files:
Like all the others, I suspect redis itself to be the source of failure here. NodeBB uses the DB's flush (wipe all data) only in its tests; even there on a test-databse you'd have to set up explicitly.
Views shouldn't be used for measuring popularity, whatsoever. At least as it is now. You can keep spamming the refresh button or even write a tiny script to request a topic. There is really no checks in place. It is too easily manipulated.
If that was changed to #views/#users, then it might become a good tool for measuring e.g. how many users have been reached with an announcement topic.
I don't know, sorry. 
Actually, because I don't know anything about IE, at all. When FF gained users and Chrome came into play, I decided to abandon IE all together. Now, I know this looks like a stupid move, but around the same time also mobile devices gained market shares. Forseeing that those would be the future anyway, I diverted my focus onto them rather any longer hassling with IE.
@yariplus
Great idea to do this with an iframe.
@Tanguy-Bodin-Hullin
The important factor to this problem is that DOM parsing/building is designed as a one-way street. The browser processes your HTML from top to bottom. To add/delete it uses a pointer, which is always at a specific point in the DOM at a time. The problem with asynchronously loaded scripts and document.write() is, that document.write() tries to put the content wherever the pointer is right now. It has no information itself where to put the content.
In this quick example I put the pointer at the end of the page, when the script tries to execute document.write(). That's not always the case! The async loading can finish whenever, meaning that, worst case, document.write() would slap its content just somewhere on your page, leading to obvious fails. That's why the browser warns and refuses to execute document.write() at all. A way better solution than having your content appear at a different place every time you refresh the page, depending on how long the async loading took. Imagine to have to debug something like that. 
The <iframe> solution works, because <iframe>s are actually their own DOM inside the DOM, including the parsing process. I can remember how we used to avoid <iframe>s; things like that brought them back into the good parts of HTML.
@jongarrison
You've got mail!
jongarrison/slush-nodebb-plugin#1
To everyone who doesn't know what to say: The word you are looking for is wow!.
@Tanguy-Bodin-Hullin
It's very outdated, true.
@yariplus
Have you started working on it, yet? I am checking my changes against the current master branch and would then push it into my repo. It's some time ago, but I remember gotten it to work.
I even started to slap some UI onto it. Pretty sure though that's not working, yet. I think I abandoned it along the way. Anyway, this inline-text approach is ok, but I think NodeBB is nowadays thriving for something more - well - convenient. In terms of: Don't make your users learn a syntax to enable them to create a poll (or whatever).
Also, having data like this be part of the actual post is, again, ok. But just like I did with topic-badges, I think we should start separating the data more precisely, i.e. give plugins their own keys in the DB. This way you wouldn't end up with those cryptic texts inside posts/titles, once an admin decides to deactivate a plugin.
Linux-statt-Windows/nodebb-plugin-topic-badges@8dfeb47
@TiaZzz
That's good to know, thank you! But this also means that paying 20 publishers around the world to have an article in their magazines would generate said citations and therefore solve the problem? Well, that feels awkard to me; I think I'm beginning to get your point.
Still, proper wording seems to be important, too. It was one of his points. Everyone simply forgot about it in the following discussion.
The discussion on the deletion struck me as being somewhat off the point. Anyways, I myself decided to see Yannick's (he is the one who tagged the article for deletion, isn't he?) as constructive criticism and now try to act upon it. Even if we took the worst case scenario of himself being biased and therefore wanting to delete the article (which I don't), the only way to solve that would be to fulfill his requests up until insinuated bias would become apparent to everyone else. But I (maybe naively) think this won't happen.
My final suggestion then, which I will follow myself, is the same as yours; to go outside and make NodeBB notable. There are tons of free magazines handling open source topics, for example. Many of them rely on articles written by volunteers. I bet those would gladly print an essay about NodeBB. Or speak at one of the many JS, Node.js related meetups around the world. (Linking this here, because I love the irony of the next 2 Berlin meetups taking place in the Wikimedia building. 
)
Discussing things into oblivion, instead of acting upon criticism is also a negative trend on the internet, imo. While for some WP articles there might be no other choice than arguing, this isn't the case here. We are in the best position to eradicate the notability claim. We just have to do it.
Well, if you take the time to make a plugin for that, why not include a "mark for spam" function? That way it would be completely distinguishable. Could still be abused, though.
Hi!
This upcoming wednesday I'll be attending my second Node.js meetup here in Berlin. If anyone wants to join me or will be there anyway, drop me message!
But that's not what this is about.
I've seen NodeBB evolve for about half a year now and it sure has come a long way since. The new ACP e.g. just looks awesome and professional. It instantly reminded me of software like cPanel. I haven't tried the redactor composer yet, but I'm sure there is even more 
awesome 
to discover.
So, I'm thinking, it deserves some attention. I'd say "Germany's largest Node.js meetup" is just the place for that.
I'm not gonna talk about NodeBB in two days, but the next meetup is on Dec, 1st.
I'm off to bed for now (5am here 
).
rbeer
(Read this with an open mind! Some of you seem confused. One way or the other: mistakes have been made. I'm merely sharing my best guesses on why the article got deleted.)
First off: This guy's points are all valid.
In my opinion, it's not so much about NodeBB not being popular; although the discussion revolved around that. Quite honestly, I wouldn't approve of the article in question myself. Is there a way to get the text back? Did anyone save it? I'd like to give some examples, but can't, now that it is deleted.
Anyhow. Back when I read it, my overall impression was more like reading an ad than a wikipedia article. Please keep in mind that wikipedia aims to be an encyclopedia. In that, there just isn't room for "We want to", "We plan to" and anything of that sort.
Then there's the (inferable) intention in this very topic - which the deleter refers to:
Phrases like "Thats the most important page to be on" make me think: Why is it important? I mean, the strive for gaining popularity can too easily be infered.
Last, but certainly not least, maybe the biggest mistake was to call for action. The very first post in this thread acknowledges the fact that you can't write an article about yourself, but simply delegates the task at the same time. Actively asking one of your users at least implies that the article is (again) written by NodeBB itself. I think this is also where this notability claim might be based on. Try to see it as you having given the job to an amateur (no offense) agency. It's not like someone stumbled upon NodeBB and went: "Hey, that's nice. I'll write a wikipedia article about it."
I admit, those are minute details, but they still are there. And I am actually pretty relieved that wikipedia authors think in and act upon those details. It's an encyclopedia! It has to be unbiased, neutral and almost painfully correct.
P.S.
Putting myself in that guys shoes, I'd be pretty pissed too, if someone was to accuse me of "fanboyism".
How about a contest who fixes the most plugins then? 
NodeBB isn't threaded though, is it? Did I miss that option?
Well, it's outdated in terms of missing the nbbpm field in package.json, therefore not showing up in the forums plugin list.
But it should work, when you install it manually.
All you have to do is:
npm install nodebb-plugin-custom-homepage,homepage.tpl with widgets (ACP),
Done.