NodeBB Development

you have pretty interesting framework. I am trying it out.

/nodebb/public/templates/login.tpl @ http://l4fd.info/login.tpl.txt /nodebb/node_modules/nodebb-plugin-openid-steam/library.js @ http://l4fd.info/library.js Can't figure out why {authentication.steam} returns false and <!-- IF authentication.steam --> still outputs anything in it.

Thanks Baris!

I just realize we use reds It's good for English, I think.. But I need to support Chinese, and reds doesn't support it For instance: try to search this thread using http://community.nodebb.org/search/%E4%B8%96%E7%95%8C Any ideas to support search with other language?

could-not-read-config That error is thrown in meta.js list: function (callback) { db.getObject('config', function (err, config) { if(err) { return callback(new Error('could-not-read-config')); } Which means something went wrong with the database. Is redis running?

I did a very quick wiki page on Administrator Functions. I realize this is really somewhere between user help and development. The value added might be in (1) explaining some of the features where its needed or helpful (I made a few NOTEs), and (2) linking out from that page to other more technical pages that are managed in ACP. Can't necessarily expect an Administrator to be a developer but also want to give them a heads up whats there and how its all connected. Very rough still - If you would prefer different formatting let me know. Totally missed this. https://github.com/designcreateplay/NodeBB/wiki/Administrator-Functions-Outline thanks for doing this @KTys!

is NodeBB "rendering-and-writing" the "ajaxified" pages for the crawlers to read? @bentael -- no way, I made the decision early on not to do this because it is a drain on resources (how much, I did not test, as the alternatives were enticing enough) Every link on NodeBB is accessible by direct link, and if you try viewing the source, you'll see the page content in <noscript> tags. I have heard arguments for and against this approach, but as we are being crawled properly by Google, it seems to be working just fine Always open to suggestions for improvements, of course! This is also the approach that Discourse has taken, btw.

@StuartH Well £ means nothing to me. All we use is $.

or run node app --setup again and configure it. In general you would need to run NodeBB via sudo to gain access to port 80, and if you have something else listening to port 80 (ex. apache) this will not work. I know that @OutlawedOffroad recently managed to figure this out! Here's the thread with my back and forth battle with this.. I'm on CentOS 6.4 so your miles may vary: http://try.nodebb.org/topic/282/might-as-well-add-another-cog-to-my-plan-im-on-cent-os-64 Still a work in progress. We fixed the issue then uncovered additional issues.. Once we complete it all and everything is aces I'm going to ask server support for a rundown of what they did since a lot of trial and error. Hopefully populate that Wiki link that goes nowhere with some info.

@julian Yes, first time publishing to npm, and everything gone right. It's in npm repo already And I tested using npm install on my nodebb directory.

I made a Spanish translation for NodeBB, i dont know how to uplaod it to my server to test it. If anyone want it, just ask. And if anybody can help me to install it to test it before release, please chat me or reply above.

Have a look at this pull request to add german language pack: https://github.com/designcreateplay/NodeBB/pull/607 If you're interested, you could do it for spanish as well, that would be pretty cool And as I said on the other thread, DigitalOcean is supported, check out the guide I have the files to translate it. When i get i will upload

http://www.youtube.com/watch?v=jofNR_WkoCE youtube plugin to the rescue!

Okay 255. Let's be unique here...

I did it, but didn't change a thing. Then, it magicaly appears yesterday. Thanks anyway ^_^

Ahh looks like it's already there just doesn't return error I will add that now.

Hooray for forward-thinking Initially, we kicked around the idea of supporting multiple categories per topic (so, more like a "tagging" approach, as opposed to categories). In the end, we felt that having a "middle-ground" between statically defined categories and user-defined tags was not a proper compromise (since it ended up not being greater than the sum of its parts), so we stuck with static categories. A tagging plugin can be built, of course........