I've finally released my new site with nodebb 2 days ago, so I wanted to make this list bigger. There is more and more people using nodebb and it's nice to see that. It's an Esport/Game community, I've only customized a bit nodebb to match the design of the site.
Alex
Posts
-
Who is using NodeBB? -
Option to hide topics with an NSFW tag.A switch in the header for this feature would be nice. About the flag system, I think if an admin flag a post as spam, the posts of their user should be purged and the user banned. For the others, a confirmation should be required from an admin or a moderator.
You both had a great idea
-
Very weird behaviour when hosting multiple instancesThe first thing that comes in my mind (I am sure that I'm wrong), is maybe due to sockets?
-
[nodebb-plugin-vine] Vine EmbeddingNice plugin , vine videos can become really viral so it's cool to share some of them if you've got a media category for example.
-
unable to save blog comment settings -
[nodebb-plugin-adsense] Google AdsenseIs it not possible each time a page has got a new focus, it reloads only the ad block with a js event? I don't know if I am clear ^^
-
[SOLVED] Issue with some plugins in ACP v0.5.2 -
dashboard acp very high cpu -
[SOLVED] Issue with some plugins in ACP v0.5.2It seems to be a bit laborious to fix it
-
[SOLVED] Issue with some plugins in ACP v0.5.2Ah you too? I thought I was getting crazy, imgbed neither works for me. Well any plugin which parse content doesn't work for me excepted Markdown Parser
-
dashboard acp very high cpuDon't worry you don't bother me @peter. You simply need to execute those commands:
./nodebb stop git fetch git checkout master git merge origin/master ./nodebb upgrade ./nodebb start
-
dashboard acp very high cpuI'm new to nodebb too and i'm still learning. I guess the version 0.5.1 should be used for production as it's flagged as stable but the version 0.5.2-dev from the master branch correct some bugs present in 0.5.1.
For my part I just use the version 0.5.2-dev currently because the bug which cause a crash after a restart from the acp and get stuck has been fixed in this version.
-
dashboard acp very high cpu@julian mentioned this problem on github https://github.com/NodeBB/NodeBB/issues/2202 but he fixed it. Are you running the latest version of 0.5.2 ?
-
[SOLVED] Issue with some plugins in ACP v0.5.2Hey @peter, unfortunately it didn't fix the crashing issue when publishing an article from wordpress to nodebb. Each time I press the button on wordpress it still crashes and get this in the console:
Error: Can't set headers after they are sent. at ServerResponse.OutgoingMessage.setHeader (http.js:689:11) at ServerResponse.header (/home/www/nodebb/node_modules/express/lib/response.js:662:10) at ServerResponse.res.location (/home/www/nodebb/node_modules/express/lib/response.js:776:8) at ServerResponse.redirect (/home/www/nodebb/node_modules/express/lib/response.js:815:8) at /home/www/nodebb/node_modules/nodebb-plugin-blog-comments/library.js:166:10 at /home/www/nodebb/src/topics/create.js:164:5 at fn (/home/www/nodebb/node_modules/async/lib/async.js:641:34) at Object._onImmediate (/home/www/nodebb/node_modules/async/lib/async.js:557:34) at processImmediate [as _immediateCallback] (timers.js:345:15) info: [app] Shutdown (SIGTERM/SIGINT) Initialised. info: [app] Database connection closed. info: [app] Web server closed to connections. info: [app] Shutdown complete. [cluster] Child Process (14399) has exited (code: 1) [cluster] Spinning up another process... [cluster] Child Process (7088) listening for connections. [cluster] Child Process (7088) listening for connections.
The post has been successfully published to nodebb though.
For the modification I made in the plugin it's simply in "node_modules/nodebb-plugin-blog-comments/public/templates/comments/admin.tpl" line 29.
-
[SOLVED] Issue with some plugins in ACP v0.5.2@julian I found the problem, it's not the ACP. The plugins I mentioned "Blog Comments, Facebook SSO, Twitter SSO, Steam SSO, Google SSO and Emailer Local" uses this in their admin template:
require(['forum/admin/settings'], function(Settings) {
I changed it to:
require(['admin/settings'], function(Settings) {
and now it's working fine, it retrieves the info from the db and the save buttons works.
-
[SOLVED] Issue with some plugins in ACP v0.5.2Hey @julian thanks for your quick reply. As it's happening with all the SSO plugins like the Facebook one you made, I thought you would maybe have got an idea
-
[SOLVED] Issue with some plugins in ACP v0.5.2I am wondering if it's a general issue or if it's only me. @julian is it working fine for you?
-
[SOLVED] Issue with some plugins in ACP v0.5.2Lavender is version 0.1.11 and Vanilla is version 0.1.17.
-
[SOLVED] Issue with some plugins in ACP v0.5.2Hi, I moved to master because of the crash restart issue on v0.5.1 but now I've got another problem with v0.5.2.
In the ACP, when I go to some plugins like Blog Comments, Facebook SSO, Twitter SSO, Steam SSO or Google SSO, the fields are blank because nodebb doesn't seem to retreive data from the database (redis). Even if I try fill them again and save, the button doesn't do anything and nothing appears in the console or logs.
I tried to reinstall nodebb several times, even if the Blog Comments is the only one enabled, I've got the issue. When I start on v0.5.1, the fields are automaticaly filled up from the db but they're blank in v0.5.2.
A strange behavior is when I go to wordpress for example and hit "Publish to Nodebb", it redirect me to the error page where it says I need to be administrator or being part of the publisher group, but nodebb doesn't respond anymore and loop this error in the console.
_maxListeners=10, members=[], domainThrown=true error: domain=null, error=function (err) { return callback(err);
Once I restart nodebb, I see the article from wordpress which has been published to nodebb in the right category (without being set in the ACP) and the thread has got like 570 replies with the same article.
Any idea about what's going on please?
-
German Installation on VserverSorry I don't understand neither speak german.
I guess you're using Apache, so you need to use it as a proxy for nodebb. Install mod_proxy_wstunnel for apache 2.2 https://www.amoss.me.uk/2013/06/apache-2-2-websocket-proxying-ubuntu-mod_proxy_wstunnel/
and add this for example in your vhost file in apache (/etc/apache2/sites-enabled/000-default ?):
<VirtualHost *:80> ServerName yourdomain.org ProxyRequests off <Proxy *> Order deny,allow Allow from all </Proxy> ProxyPass /socket.io/1/websocket ws://127.0.0.1:4567/socket.io/1/websocket retry=0 ProxyPassReverse /socket.io/1/websocket ws://127.0.0.1:4567/socket.io/1/websocket ProxyPass /socket.io/ http://127.0.0.1:4567/socket.io/ retry=0 ProxyPassReverse /socket.io/ http://127.0.0.1:4567/socket.io/ ProxyPass / http://127.0.0.1:4567/ retry=0 ProxyPassReverse / http://127.0.0.1:4567/ </VirtualHost>