Technical Support

It works fine when in 0.6.x. So it must be a bug in 0.7.x

I just pulled the latest commit and it seems to be working now. Yessss, thank you. (ﾉ´ヮ´)ﾉ*:･ﾟ✧

Hi,

It looks like rhc app create nodebb nodejs-0.10 command did not create nodebb directory.

Please make sure, that you're running commands on your own computer, not through ssh on OpenShift side.

Try to remove nodebb from your OpenShift account and start from scratch.

Calling git init may seemed like it helped, but it created local only repository, which was not connected with any of the others (OpenShift, NodeBB and openshift-nodebb). That is why git push origin master did not work - origin remote was not configured.

@nhl-pl and @julian , all is cool as they say, got help from digital ocean and am good to go now, thanks again to you both for helping - the post is here for anyone else that's looking.

regards, Lee 😁 😃

Perfect thanks

If you install mongo via apt, I believe it is mongod, but via the 10gen repository, it is mongodb

A more quick solution:

Change

.container-fluid {
.container-fixed();
}

to

.container-fluid {
.container;
}

in nodebb-theme-vanilla/less/bootstrap/grid.less

@aixnr Thanks u 🙂
It works now

@Mega said:

I'll check that today-tomorrow and will post here.

aight
doesn't reproduced anymore on latest

Hello @julian,

After I've updated to the latest commits. This issue resolved now. Thanks for your help.

Easy solution would be the old RTFM method? 😛

@baris thank you for your help 😆 . nodebb is a very excited project

Thanks @baris !

You can use apache too, but Nginx is a nicer experience.

Here's the guide for 2.2.xx

Thanks Julian!
Mark thread as solved, working as intended, was just looking for this function inside the admin panel instead of the normal user view 😉

@psychobunny is a real superstar, but the community as a whole (users/developers) is real good one. Which is why I personally would stay with NodeBB over say Discourse, which I would say would be NodeBB's only real competitor.

Feel free to add a pull request for this if you haven't already 🙂

I believe you should have as many partials in your main template as efficiently as possible to cut down on redundant code. Here I'll write the standard for a good rule of thumb on how you should organize your templates and all the code within in them.

Any redundant JS scripts should be in their own partial to be reused in other templates if need be.

Take full advantage of the NBB API so that you extend your template even further. For example using <!-- IF loggedIn --> condition can greatly improve UX and conversions rates on your site. Having some type of call to action or banner within these will let the user know that they aren't logged. OR when they are logged in, show something else. You can come up with some pretty crafty ideas. But yeah, do what you can with the existing API.

You can only do so much with the templates but is that good enough? Maybe, maybe not, but it does work when you plan out the logical flow and hopefully not get lost in the div's and such. For example on the Majestic Theme, the topic covers are pretty complex and one can easily get lost in the flow of what's going on. Here's a screenshot of the topics UI.

Screen Shot 2015-03-17 at 8.12.29 AM.png

Now lets take a little peek at whats under the hood;

Screen Shot 2015-03-17 at 8.16.46 AM.png

Screen Shot 2015-03-17 at 8.14.33 AM.png

Now there's way more to this, but this is just a little example of how I control the topic covers. The only reason why I'm posting this is because I'm quite certain it would take a while to replicate without all of the other partials in this one template (not shown for obvious reasons).

You can also do stuff like this to take control over pluralization of your template: post<!-- IF !topics.unreplied -->s<!-- ENDIF !topics.unreplied -->
Which would mean, if you don't have any posts, remove the s in post, otherwise its posts. Neat huh?

Anyone else have any cool things they've done with the template system so far in their existing theme? Share some of your ideas here. 🙂

In the end, here are the only changes (to the original theme) I did to successfully achieve what I wanted without bug:

It works.