@julian said in Debugging nodebb:

Looks like you already have a NodeBB instance running... or maybe something else running on port 61236.

Try checking out ps aux | grep node and killing off the other NodeBB process, if there is one.

Thanks to @ben_lubar I was able to get this working. Turns out I needed to start app.js not nodebb because nodebb would fork and screw up the debugging.

People on my forum noticed the same thing. I told them that one is quick search and one is advanced search, but the confusion about the buttons looking the same remains.

@teh_g said in Scrolling doesn't work on pinned threads on mobile.:

@dangeruss It might be a limitation on that Android version?

What would be? I think maybe my version of android is sending a different touch signal then higher versions of the OS. I don't know much about mobile site development, but I believe it's not click they're listening for? Do you guys know where the code is for the rearranging of the pinned threads?

@julian tested it on the same chrome version as me and it worked fine on a galaxy s7 edge.

Still doesn't work for me on the galaxy s5.

@julian that's really weird. I'm on chrome 61 on android 5.0 lollipop. Now I know how my users feel when I tell them u can't reproduce their bugs.

Should I post a video or something?

@julian said in Scrolling doesn't work on pinned threads on mobile.:

Hey there -- browsing your site on Chrome on my Android device, I'm not experiencing any scrolling issues. What browser are you using?

Chrome on android.

The issue happens when you put your finger over one of the pinned threads and try to scroll down. The only way it scrolls down for me is if I put my finger on one of the sides.

I see on desktop if I try to drag that post title it tries to rearrange it, so perhaps that feature is interfering with mobile?

@psychobunny @julianlam Should I file a bug report on github?

We have a couple of pinned thread and when you try to scroll down on mobile it doesn't scroll if you put your finger on one of the pinned thread titles.

We're on 1.6.1. Could be related to the previous bug fix with scrolling tables.

Example:

@julian said in Debugging nodebb:

Looks like you already have a NodeBB instance running... or maybe something else running on port 61236.

Try checking out ps aux | grep node and killing off the other NodeBB process, if there is one.

Thanks to @ben_lubar I was able to get this working. Turns out I needed to start app.js not nodebb because nodebb would fork and screw up the debugging.

I'm trying to figure out how to write a plugin, so I'm trying to set up a development environment so I could step through code.

I tried webstorm, but I'm getting the dreaded EADDRINUSE error

Debugger listening on [::]:61236
Error: listen EADDRINUSE :::61236
    at Object.exports._errnoException (util.js:1020:11)
    at exports._exceptionWithHostPort (util.js:1043:20)
    at Agent.Server._listen2 (net.js:1258:14)
    at listen (net.js:1294:10)
    at net.js:1404:9
    at _combinedTickCallback (internal/process/next_tick.js:83:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)

Here's the command line that webstorm runs.

"C:\Program Files\JetBrains\WebStorm 2017.2.4\bin\runnerw.exe" "C:\Program Files\nodejs\node.exe" --debug-brk=61236 --expose_debug_as=v8debug C:\web\nodebb\NodeBB\nodebb dev

@pichalite said in Topic Alerts:

@dangeruss you can create a plugin to achieve that functionality.

Thanks, can you give me some pointers? Like which functions I would call and what hooks I should implement?

Our users would like to be able to get notifications both in the menu bar as well as by email of any topics (perhaps in certain categories) which match keywords.