After some more research, I found a solution: .topic [data-username="USERNAME"] .poster-avatar Will select just one user's avatar

@frissdiegurke said in IP displaying on feeds and mentions: Check the url within config.json. Well, that was easy. Thanks for the quick fix!

btw, on nodebb 1.2.1 the 2 lightbulbs are fixed it's now 1

With new 1.15.2 nodeBB, there are some bugs in the night mode, we have just installed 1.15.2 in our development forum, so I will fix all bugs in the coming weeks and create pull request to the plugin in github... For those who needs a quick fix, you can add these codes to Custom CSS session in NodeBB for most obvious problems. body.lights-out { .topic-list-header { background-color: #191919 ; } .recent-cards .recent-card-container .recent-card { background-color: #2E2E2E ; border: #848484 ; } .tag-list .tag { background-color: #404040; } }

@Arc It's great! Thank you very much for this, I included it in my forum immediately

Lately, I've been tweaking my site to improve touch capability- and have been eyeing a couple features. Its possible for forum owners to add these themselves, but some of them really might wanna be core. Touch Sidebars are really needed: https://github.com/jakiestfu/Snap.js Something like fastclick might be nice: https://github.com/ftlabs/fastclick And I've yet to find a clean way to do it, but many web apps send push notifications on android- would that be possible to integrate?

@frissdiegurke Thanks! Thankfully, Pichalite was able to talk me up to 0.7.3, now we're trying to get up from there.

What is the main point, when you visit Unread section, to open topic from the first message? One possible solution: Add button (btn-default) near title, with clear message (go to unread message) Have much more possible solutions? - add settings to the ACP. Every community will select most UX friendly for them.

@Arc Yeah, housing is cheaper, jobs are more plentiful and pay better for a software engineer, and overall the community has more going for it in Kansas City. In terms of my life, things are much better here. I do miss family, the mountains and skiing though. But I can vacation in Colorado to visit those things.

Just using https://community.nodebb.org/me should work now as well.

Thanks for the personal reply, @a_5mith . Restarting initially appeared to fix the issue, and actually has fixed that issue, but suddenly now its turning every single link into an attempted imbed. I didn't change anything, at all, except run a restart, its worth noting. http://coloradorks.com/topic/22/animas-river-no-longer-liver-failure-yellow-safe-for-use-again It was working, then suddenly over a restart it stopped working, and now its gotten over eagar and is trying to pick up every link as an embed. As for nodebb version and plugin version, they are respectively: NodeBB v0.7.1. NodeBB Youtube Lite Plugin - Installed 0.4.1 | Latest 0.4.0

Okay, so I fixed it. Put the tags in the header as usual, then upload the smallest (16x16 as ico) to the general section. This will be the one that nodebb overrides the others with. The others will still work for other systems like android and such.

As I am a irreparable idiot, in the pursuit of messing with my Lavender/Persona hibrid theme I in some likely unrelated way totally destroyed everything. I was messing around with CSS, hit restart, and the server went down, hard. And hasnt come back since. I've tried restarting the server, running nodebb resets for widgets, themes, and plugins, restarting nodebb what must be 50 times. The log output I'm getting is: Clustering enabled: Spinning up 1 process(es). 26/7 19:57 [1252] - info: Time: Sun Jul 26 2015 19:57:53 GMT-0400 (EDT) 26/7 19:57 [1252] - info: Initializing NodeBB v0.7.1 26/7 19:57 [1252] - error: [meta.dependencies] Could not read: nodebb-plugin-spam-be-gone [cluster] Child Process (1252) has exited (code: 0, signal: null) and when I try to access the page, I get a: This webpage is not available ERR_CONNECTION_REFUSED I assumed this was a redis issue, so I tried restarting redis to no efffect, I know I disabled the emoji plugin so tried to reinstall it via SSH but it didnt help. Any suggestions for getting this back up and running? Edit 1: Tried running npm install to see if it could be some update issue, will update with results. Edit 2: running npm install appears to have fixed it. Future people with this issue, use NPM install and dont be an idiot like me resetting everything.

Hmm, That should work, as long as you changed all the identifiers. I've done the same thing with my own themes.