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?

@Drew-Llewellyn I've got the following error:

ver. NodeBB v0.6.0.

@xuso thumb up!

@José-Ángel-Rey-Liñares That's because of connection to Redis could not be established
have you tried command: redis-cli $REDIS_CLI

[Update] Try to execute: node app.js (not node app.js --setup)

And one more.
I can predict that websockets won't work in scope of defined socket io transports on openshift. The only long polling is running there (Chrome > F12(browser inspector )> Network : will demonstrate it for you.).

It's because openshift allows websocket connection with the port 8000 only.
In order to get it work just add the following line in your config.json:

"socket.io": {
"address": "http://nodebb-XXXXX.rhcloud.com:8000"
}

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

@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.

@TILT Absolutely right!

@TILT hi
The only solution I found is to hack webservers.js file by overwriting the port and IP variables with the respective $Openshifts variables

@Ted said:

@Tom-Riddleff you can still run Cloudflare for DNS management, but you can't allow it to cache/minify content for the domain.

Yea. And I've done so. Moved back to Cloudflare, but swithed 'cloud' off for nodebb hostname.

@julian
On Redis side - every thing OK. Respective keys and values on their places.
After some investigation I found that the problem acctually in Cloudflare, which I use. It supports websockets on 'Enterprise' plan, which I don't have.
So I swith that off.
And everything works like a charm