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

https://phatwalletforums.com/category/6/hot-deals

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

@pitaj said in "Object doesn't support property or method 'try'" with 1.6.1:

I just tried it and didn't have any issues. I'd suggest trying ./nodebb build

Thank you, that seems to have worked. Not sure if I missed a step during the upgrade, or if permissions (I did the upgrade as root, but it runs as a service user) stopped it from doing a proper build on startup.

IE11.

Windows 10 (possibly others). The forum is unusable. Only refresh works, clicking around breaks with the following error on the console.

[deprecated] Accessing benchpress (formerly known as templates.js) globally is deprecated. Use `require(["benchpress"], function (Benchpress) { ... })` instead

SCRIPT438: Object doesn't support property or method 'try'
benchpress.js (187,5)

@julian I think there's some front end hook that I would need to call here, is that right?

@julian said in Large tables not vieweable on mobile:

@dangeruss You can always pull down the latest commits from master if you don't want to wait for a release. It's a little riskier since regressions may occur, but then you will get the latest features too

Yea I kind of want my forum to continue working.

Is this going to be a nodebb update or a update to the theme? If a nodebb update, then am I correct in assuming it didn't make it into 1.6.1?

@julian said in Underscores in links:

To be honest, it kind of sounds like a bug with the markdown parser...

So is this a bug we can file with what I assume is a third party parser?

@pitaj said in Underscores in links:

Not if you use a named link, or embed the image. It's markdown, learn it.

Yes, there are workarounds, but are you saying that it's normal for these links to break? It' s a markdown thing?

https://images-na.ssl-images-amazon.com/images/I/51EtOeH0iJL._SY300_.jpg
becomes
https://images-na.ssl-images-amazon.com/images/I/51EtOeH0iJL.SY300.jpg

Is there a supported way of doing Apache clustering, or should I start migrating to nginx?

Our community would like a wiki area where the thread can be summarized/important points highlighted by members of the community. Any registered user should be able to edit it (and history would be nice, as well as locking by moderators in case it gets out of hand).

@julian Sure. This one for example:

https://www.anrdoezrs.net/am/1234567/include/allCj/generate/onLoad/impressions/page/am.js