General Discussion

I decided to add icons in the notification (fortawesome). function(_followers, next) { followers = _followers; if (!followers.length) { return callback(); } title = postData.topic.title; if (title) { title = S(title).decodeHTMLEntities().s; } notifications.create({ bodyShort: '[[<i class="fa fa-share"></i>, notifications:user_posted_to, ' + postData.user.username + ', ' + title + ']]', bodyLong: postData.content, pid: postData.pid, nid: 'tid:' + postData.topic.tid + ':pid:' + postData.pid + ':uid:' + exceptUid, tid: postData.topic.tid, from: exceptUid }, function(err, notification) { if (err) { return next(err); } if (notification) { notifications.push(notification, followers); } next(); }); }, <i class="fa fa-share"></i> - this icon. The problem is that it appears as - &lt;i class="fa fa-share"&gt;&lt;/i&gt; < > Are displayed in the form of html code.

Unfortunately nothing helped.

@markcarey I created an OAuth2 endpoint on my website from scratch and made NodeBB utilize it successfully. It was the first time I engaged in such an endeavour and it wasn't easy! I followed the examples provided in the OAuth2orize plugin's github. Besically all you have to do is swap out the local db they use and implement your db logic. Also use some sort of UID generator for client ids/secrets. If you have that done and are able to successfully authorize with some tool, for example Postman or the Google OAuth Playground it should be pretty straightforward from there to setup the NodeBB SSO OAuth plugin to fit your website.

Ok, so if i need auto numbers i can do this 1 1 1 1 followed by a . Or is there a better way todo this?

@julian We would love nothing more to put into nodebb but we're still bootstrapping in our (still small) startup. I was just wondering if the different elements of a Q&A had already been implemented in one form or another in NodeBB, so we could put them together for a Q&A forum we want to provide for our users.

@julian can this (redirect all HTTP requests to HTTPS) be done with Apache?

You probably need to be more specific with your rule selector (the 'a' part). If another rule is more specific, it will overwrite yours. Examples: An 'a' tag with a class: a.someclass An 'a' tag as the child of a 'div' tag: div > a An 'a' tag after a tag with an id: #someid + a If any of such rules exist, they will overwrite yours. You can see what rules are active in most browsers by right-clicking something and choosing 'Inspect' Other things: Make sure the little checkbox 'Use Custom CSS' below is checked. Try restarting nbb and clearing your browser cache if nothing else works.

@Fastidious On the more real side, Who knows... Maby the web wont advance after a year or 10. We will never know.

I know this is old but it came up when I was looking for an answer, so for those that come after..... Redis is already on c9 and its old. Following is some quick instructions that get it working but please understand i REALLY DONT know what Im doing The instructions are base off... https://www.digitalocean.com/community/tutorials/how-to-install-and-use-redis Remove the old redis stuff Do you need to do this?...no idea $ sudo service redis-server stop $ sudo dpkg -P redis-server $ sudo dpkg -P redis-tools Download and make the new Redis 3.0.x paez@nodebb:~/workspace $ mkdir redis $ cd redis wget http://download.redis.io/releases/redis-stable.tar.gz tar xzf redis-stable.tar.gz cd redis-stable make sudo make install Install During the install the default path for where to put the executable s was wrong and I think it was /usr/bin/ Also, select port 16379, because the old redis is still running and Im still not sure how to turn it off properly. But your new one will work fine if you set nodeBB to the new one. I did get rid of it once, but not exactly sure how. cd utils sudo ./install_server.sh And now you should have a working redis on 0.0.0.0:16379. Still have the old one running, as I dont know how to get rid of it properly yet. I tested this with the latest NodeBB and was able to get it to work except I get this error in the console.... WebSocket connection to 'ws://nodebb-c9-paez.c9.io/socket.io/?EIO=3&transport=websocket&sid=Gn4rDgj2XlEILV0FAAAA' failed: Error during WebSocket handshake: Unexpected response code: 400 ...and a whole bunch of.... [deprecated] variables.set is deprecated, please use ajaxify.data... ...dont know why and am not likely to find out as Im going to be running it off Openshift, but this hopefully gets someone a little closer....and it does seem to work good enough for theme mucking which is what I wanted the c9 one for.

Currently: [image: RgMEVye.png] Unread on top: [image: iyMLenK.png] Thus, the user will never lose unread alert throughout the list. @administrators

@psychobunny wouldn't you agree this should be part of core?

Yeah I agree at the least the bars shouldn't show up if its a link category. @psychobunny

Well, just sharing my manual yet working solution, I just stop the NodeBB process and do everything manual from there, including backing up my NodeBB folder and Redis DB.

@julian No. Not really sure what else I can do except to maybe rebuild the whole server. I'm just running the upstart script with ./nodebb start for now. IIRC, the major drawback to that was that it doesn't write the PID to a file and so you can't make an orderly stop to the process, which is not ideal, but it will work for me for now.

@jarey I tried that cartridge and it wont install at all...check the issues. Got it working!!!! (NodeBB that is) http://nodebb-paez.rhcloud.com/ names prolly gonna change to forum if that links doesnt work. Try these two..... https://github.com/icflorescu/openshift-cartridge-nodejs https://github.com/transformatordesign/openshift-redis-cart One problem I only just noticed trying to install nodebb was that nodejs wasnt actually finishing its compiling....that prolly caused a bunch of my probs...mainly the liwp not working. That redis is at 2.8.13 so up to date and is forked off the one recommended.

@BDHarrington7 Greaaaat! Thank you very much for the fast answer.

Its possible to assign a group the moderating power on just one category, However be aware that this will also include other moderation powers such as Forking, Closing and Moving topics.

@ogerly said: there is information about the merger of nodebb and ghost ? Not merging, but can be used with each other.

Mystery man/woman made a pull request that we merged into the Redactor plugin: https://community.nodebb.org/topic/6093/official-plugin-redactor-composer-now-available-in-0-7-1/ They're the first developer to make a pull request against the plugin and deserves some props! Thank you philburr! =D Here is footage of them (or someone who looks like them, or someone that doesn't) coding: [image: lz7hOlC.gif] Do you know who (on our forum) this is? https://github.com/philburr If you're able to contribute to the plugin please hack away The github: https://github.com/NodeBB/nodebb-plugin-composer-redactor The npm: https://www.npmjs.com/package/nodebb-plugin-composer-redactor

@pichalite said: Every time I do an upgrade it does not go well. There is always some kind of error even though I am following the upgrade process from the docs. Same here. Haven't had one work yet, actually. Not since 0.3 I think.