I'm using Persona theme and try to find any solution how to make footer sticky to the bottom.
any ideas?

hi guys!
I'm getting stuck with the launching nodebb on openshift. on the final stage when I do start the app - I get the error listening EACCES, despite I strictly follow the steps.
has anyone experience same issue?
could you please advice how can I solve it?

Thank you for your note, @julian
I acctually found what I were need.
Adding an appropriate string to config.json - solved my problem.

"socket.io": {
	"address": "http://myforum.com:8000"
}

Thus websocket will use port 8000 on establishing the connection.
One of openshift's bottleneck, that held me up.
Done

@José-Ángel-Rey-Liñares Hi!
First try to ssh your app on openshift and type:

redis-cli $REDIS_CLI

If redis cartridge installed properly - you have to get in to redis console.
Then. Compose you json.config file this way(replace appropriate data):

{
"url": "http://nodebb-myapp.rhcloud.com",
"port": "8080",
"secret": "xxxxxxxxxxxxxxxXXXXXXXXXX",
"database": "redis",
"redis": {
"host": "127.xx.xxx.xxx",
"port": "1xxxx",
"password": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"database": "0"
}
}
And upload it to openshift.

You can get the redis object data for your config with the following command:

echo $OPENSHIFT_REDIS_HOST && echo $OPENSHIFT_REDIS_PORT && echo $REDIS_PASSWORD

Then try to 'nodebb app.js --setup' your application on the server. It'll fetch all the needed data from the config.

@José-Ángel-Rey-Liñares Ok. Poke me if any.

I'm using Persona theme and try to find any solution how to make footer sticky to the bottom.
any ideas?

Hi guys!
I've tried adsense plugin with nodebb ver. 1.0.0(Persona) and encounter that ads are not displayed for mobile devices. On desktop is fine.
The same ads blocks are worked on previous version 0.6.0(Lavender).
Don't you know what's might went wrong?

@julian Thank you Julian.
Tried to debug the recentreplies.js and found that it tries to access value of category that is undefined and all other fields of the post is set to null.
The idea is to try fix it in redis before upgrading.
If you would have a chance to advice me a correct direction where I should dig in in order to delete this corrupted data in db it will be super helpful.

@baris the version is 0.6.0
I'm planning to upgrade it in a near time. And probobly move to Mongo. But for now it would be good to solve this exception in order to stop the downtime on Prod.

Thank you @nhl.pl for reply.
I run it in git rep for testing purposes only. Just tried to reproduce it on my local machine with RDB shapshot I loaded. And actually did it. Cuz same issue is on Production site.

It's definitely some entity has broken in DB, but I can't point out which one.

Hi guys!
I've got an issue after I delete the topic as admin and then accidentaly delete the message in this topic.
nodebb version is pretty old. However could you please help me to solve it?
Probaly it could be fixed throgh the database(Redis)

Guys, any suggestions?

@baris Hi!
I'm using NodeBB v0.6.0. link to sitemap.

@pitaj Hm-m-m.
But sitemap of community forum (https://community.nodebb.org/sitemap.xml) - contains topics that are live (even this topic), but my sitemap doesn't. Only removed(purged) topics are shown.
Probably there need some addition settings to be applied? Could you please suggest?

I've encountered that sitemap.xml file contains the links to topics that has been removed, but not the fresh(currently live) topics. Why it is so?